د هالٱت لٛرسن:پرۉژٱ تازٱ
ڤیکی لٛرنیئن.نت مؽها گٱپ بۊئٱ
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, a translatewiki.net staff member will integrate translation updates into your project. This requires a language addition procedure. Translatewiki.net needs access to push changes into your project (e.g. commit access with direct push or pull requests), or have access to a branch that will be noticed and merged. This ensures that the work of translators are regularly integrated.|
اؽما دۊس دارؽم
|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 JSON, Java properties, or Ruby-style YAML. Other supported file formats include Gettext, Android and iOS. Let us know if you have a different format in mind; in our experience, support for a file format is relatively easy to add, if you're proficient in PHP.|
Still interested? Good. You can contact us via,
- Our issue tracker - Phabricator. Fill out the project information section on this task template.
- Our support page. First, create an account as a developer (using the Can't submit some translations right now? option) on the homepage, wait for your account to be approved and then create a support ticket.
If you want to explore some more first, then try the localisation for developers page.