Translating:New project/zh-hant

This page is a translated version of a page Translating:New project and the translation is 12% complete.

---

Translatewiki.net wants to grow

我們期待有更多的項目 ！不要猶豫，請和我們聯繫並討論如何將您的項目加入 translatewiki.net。我們重視我們義工的功勞, 所以我們想要在未來中會被積極開發的項目。我們也強調翻譯人員和開發人員之間的交流。以下是一些我們在新項目中想要有的東西, 以及哪些項目在接受後會需要被管理。

我們需要...

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
	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
	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.

我們喜歡...

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
	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
	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. If you want to explore some more first, then try the localisation for developers page.