Difference between revisions of "Translating:New project/ms"

From translatewiki.net
Jump to navigation Jump to search
Line 5: Line 5:
   
 
<div style="float:left; max-width:46%; padding-right: 2em">
 
<div style="float:left; max-width:46%; padding-right: 2em">
== We require... ==
+
== Kami memerlukan... ==
 
{| style="width:95%; background:transparent;" cellpadding="4"
 
{| style="width:95%; background:transparent;" cellpadding="4"
 
| colspan="2" | '''Openness'''
 
| colspan="2" | '''Openness'''

Revision as of 04:42, 23 April 2011

Translatewiki.net hendak berkembang maju

Kami sedang mencari-cari projek baru! Jangan teragak-agak untuk menghubungi kami dan membincangkan bagaimana projek anda boleh ditambahkan ke dalam translatewiki.net! Kami menghargai kerja-kerja penterjemah sukarela kami; iaitu kami sedang mencari projek-projek sihat yang boleh giat dimajukan untuk masa depan yang sejauhnya. Kami juga menekankan komunikasi antara para penterjemah dan pembangun. Yang berikut ialah senarai ringkas yang menonjolkan harapan kami kepada projek baru, dan proses-proses yang perlu diuruskan sebaik sahaja projek diterima.

Kami memerlukan...

Openness
Openness 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.
 
Development
Development 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 minimised. There are multiple ways to get translations into use faster, which can be discussed.
 
Integration
Integration 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 for at least one translatewiki.net staff member. This ensures that the work of translators will actually be integrated. Translatewiki.net staff have a lot of experience of committing to various source control systems.

We like...

i18n support
i18n support 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.
 
Communication
Communication 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.
 
File formats
File formats 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 adding file format support is relatively easy for someone proficient in PHP.


Still interested? Good. Please contact us, on our IRC channel #mediawiki-i18n at freenode, by e-mail, or at our support page. Though, nothing beats good real-time chat to solve any possible issues and to get things going.