ꯋꯥꯍꯟꯊꯣꯛꯂꯤ:ꯑꯅꯧꯕ ꯊꯧꯔꯥꯡ

From translatewiki.net
Jump to navigation Jump to search
This page is a translated version of the page Translating:New project and the translation is 78% complete.
Outdated translations are marked like this.

Translatewiki.net ꯍꯦꯟꯅ ꯄꯥꯛꯊꯣꯛ ꯆꯥꯎꯊꯣꯛꯂꯛꯅꯤꯡꯕ

We are looking for more projects! Do not hesitate to contact us and discuss how your project can be added to translatewiki.net. We value the work of our volunteer translators, which means we are looking for healthy projects which are actively developed for the foreseeable future. We also emphasize the communication between the translators and developers. Below is a short list highlighting what we are hoping to see in a new project, and which processes need to be managed once accepted.

ꯑꯩꯈꯣꯏꯗ ꯆꯪꯕ

ꯑꯃꯖꯨ ꯑꯃꯖꯎ ꯌꯥꯍꯟꯕ
꯱ꯖꯨ ꯱ꯖꯨ ꯌꯥꯍꯟꯕ We only accept projects which use a free and open source license. We have to make choices in what we want to support directly. Because our origin lies in MediaWiki and Wikimedia, this is a core value to us. If your application is not free, but you would still like to use the same software, see the documentation.
ꯆꯥꯎꯈꯠꯂꯛꯄ The new project should be in active development and using a version control system. We are already familiar with CVS, Subversion and Git. The project should have periodic releases or another way to update translations. Time to get translation into use (TIU) should be minimized. There are multiple ways to get translations into use faster, which can be discussed.
ꯄꯨꯟꯁꯤꯟꯕ Once content for your project has been translated at translatewiki.net, ideally translatewiki.net staff is able to integrate the changes back into your product. This requires a language addition procedure and commit access (with direct push) for at least one translatewiki.net staff member, to ensure that the work of translators will actually be integrated. Translatewiki.net staff have a lot of experience of committing to various source control systems.

ꯑꯩꯈꯣꯏꯒꯤ ꯑꯄꯥꯝꯕ

i18n ꯃꯇꯦꯡ
i18n ꯃꯇꯦꯡ We only support the UTF-8 character encoding. Support in the i18n framework for applications for variables, multiple different plurals, and right-to-left languages is preferred. Having support for grammatical forms is something we think should always be considered, and also support for gender of the user where the user is spoken to directly or other users are mentioned in interface texts. This area is often where most problems and delays come from; try and check our Localisation for developers tips to avoid them.
ꯄꯥꯎ ꯐꯥꯎꯅꯕ
ꯄꯥꯎꯐꯥꯎꯅꯕ A developer from the project should be active in translatewiki.net to answer questions, notify about coming releases, coordinate with the project's developer group, etc. Our approach to localisation works best when knowledge flows as freely as possible between developer communities and translator communities. The project liaison plays a very important role in that.
ꯐꯥꯏꯜꯒꯤ ꯃꯑꯣꯡ ꯃꯇꯧ
ꯐꯥꯏꯜ ꯃꯑꯣꯡ ꯃꯇꯧꯁꯤꯡ The translatewiki.net system is based on translation files. Use of key-based file formats is preferred, like Java properties and Ruby-style YAML. Other supported file formats are PHP arrays, PHP variables and Gettext. Let us know if you have a different format in mind; in our experience, support for a file format is relatively easy for you to add, if you're proficient in PHP.

Still interested? Good. You can contact us via,

If you want to explore some more first, then try the localisation for developers page.