Translating:Novo pruggietto

Revision as of 06:14, 26 May 2021 by FuzzyBot (talk | contribs) (Updating to match new version of source page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search vuo crescè

Stammo ascianno cchiù pruggette! Nun perdite tiempo a ce cuntattà e a parlà 'e comme 'o pruggetto vuosto se putesse fà trasì dint'a Nuje apprezzamm' 'a fatica d' 'e tradutture vuluntarie nuoste, 'o quale vò dicere ca jessemo truvanno 'e pruggette 'n salute 'e quale fossero sviluppate attivamente int' 'o futuro prossimo. Vulimmo pure fà verè c' 'a comunicazione è mpurtante nfra 'e tradutture e 'e sviluppature. Ccà abbascio ce sta na lista evidenzianno cosa vulimmo truvà dint' 'a nu pruggetto nuovo, e quali prucesse ce vonno p' 'e putè gistiunà na vota ca chisto fosse accettato.

Tenimmo bisogno di'e ...

Apiertura Nuje accettamme sulamente pruggette c'ausassero na licienza libbera e codece apierte. Nuje amma fà scelte ncopp'a quale pruposte vulimme suppurtà direttamente. Pecché l'origgene nuoste stanno dint'a MediaWiki e Wikimedia, chist'è nu valore dint' 'o core nuosto pe' nuje. Si l'apprecaziona vuosta nun è libbera, ma 'a vulisseve traducere ancora cu stu software, vedite ccà documentazione.
Sviluppo 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.
Integrazzione 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.

We like...

'o supporto i18n
'o supporto 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.
Comunicazzione 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.
Furmato d"e file
Furmato d"e file 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.