Translating:New project/io

Revision as of 13:42, 17 October 2021 by JSantos (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search wants to grow

We are looking for more projects! Do not hesitate to contact us and discuss how your project can be added to 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.

Ni bezonas...

Aperteso Ni nur aceptas projeti qui uzas libera licenco open source. Ni mustas facar selektadi pri quo suportar. Nam nia origini esas MediaWiki e Wikimedia, to esas centrala valoro por ni. Se vua app ne esas libera, tamen vu deziras uzar ol, videz ca dokumentado.
Developo 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.
Integro Once content for your project has been translated, a staff member will integrate translation updates into your project. This requires a language addition procedure. 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.

Ni prizas...

suporto i18n
suporto i18n Ni nur suportas karakteri UTF-8. Suporto che framework i18n por varianti, multopla diferanta plurali, ed idiomi skribita dedextre-til-sinistre esas preferebla. Ni anke konsideras suportar gramatikala formi, ed anke suportar genri segun parolesas en irga idiomo uzata che interfacio. Ca areo ofte esas fonto di problemi; voluntez verifikar nia sujestaji che Lokizo por developeri por preventar li.
Komunikado A developer from the project should be active in 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.
Formati di arkivi
Formati di arkivi The 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,

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