Translating:Novi projekat

From translatewiki.net
Revision as of 09:20, 20 January 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

Translatewiki.net želi da raste

Tražimo više projekata! Slobodno se obratite nama i porazgovarajte kako vaš projekat može biti dodan na translatewiki.net. Mi cijenimo trud naših volontera prevodioca, što znači da tražimo zdrave projekte koji se aktivno razvijaju u doglednoj budućnosti. Također naglašavamo komunikaciju između prevodioca i razvojnih programera. Ispod je kratak spisak koji pokazuje čemu se nadamo da vidimo na novim projektima te koji se procesi moraju odvijati kada se novi projekat prihvati.

Mi trebamo...

Otvorenost
Otvorenost Prihvatamo samo projekte koji se koriste slobodno i imaju licencu otvorenog koda. Moramo da odaberemo šta želimo da direktno podržimo. Pošto naši korjeni leže u MediaWiki i Wikimedia, ovo je temeljna vrijednost za nas. Ako vaš program nije slobodan, ali još uvijek želite da koristite isti softver, pogledajte dokumentaciju.
Razvoj
Razvoj Novi projekat bi trebao biti u aktivnom razvoju i da koristi sistem kontrole verzija. Već smo upoznati sa CVS, Subversion i Git. Projekat bi trebao imati povremene objave ili na drugi način ažuriranje prevoda. Vrijeme za koje se prevod stavlja u upotrebu (TIU) bi trebalo biti smanjeno. Postoji više načina da se prevodi stave u upotrebu na brži način, o ćemu se može raspravljati.
Primjena
Primjena 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.

Mi volimo...

Podrška za i18n
Podrška za 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.
Komunikacija
Komunikacija 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.
Formati datoteka
Formati datoteka 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,

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