L10N/zh-tw

From FedoraProject

< L10N
Revision as of 09:11, 3 April 2011 by Zerng07 (Talk | contribs)

Jump to: navigation, search

Contents

於 L10n (本地化) 專案中貢獻的角色

Idea.png
貢獻的角色
這僅只是提供貢獻角色的建議。您可以做出超乎這裡所提到的事情,請不要被侷限住了。

Join Translator.png
翻譯者

Fedora 本地化專案

Fedora 本地化專案 (FLP) 的目標是要讓 Fedora 週邊的東西更貼近 (the Software, Documentation, Websites and culture) 當地社群 (countries, languages and in general cultural groups)。通常這包含透過 PO 檔的翻譯,但絕對不在此限。

Note.png
L10N
是「Localization」一辭的縮寫,這種縮寫方式也被稱為字數縮寫 (numeronym),是一種將單詞其開頭與結尾之間的中央字母 (本例為「ocalizatio」) 以字母數目 (本例為「10」) 來命名的方式:Localization

語言清單

請參照 http://www.transifex.net/languages/ 以概覽有多少語言可用,並且有多少語言涵蓋我們必要軟體的實質翻譯。

參與 Fedora 本地化專案

若要瞭解如何參與 Fedora 本地化專案,請參照 翻譯快速上手指引.

新翻譯者:

其他有用資源:

其他取得幫助的方式:

團隊

溝通

郵遞清單

There are some mailing lists that interest members of the FLP.

  • The main list is trans list (archive), which holds discussions about translations, team coordination, etc.
  • Some issues are discussed at i18n list. If you are interested in input methods, international fonts, etc, you would want to join this as well.

提交清單

  • We've setup the group 'l10n-commits' for those who would like to receive emails for commits in the /cvs/l10n/ repo and various other emails.
  • To subscribe, go to the Fedora Accounts System and add yourself to l10n-commits. Unfortunately the system needs approval, so someone should jump in to approve you, which should happen quickly.

IRC 頻道

會議

時程

Both of these schedules include translation freeze dates, which are dates that translations are picked up for adding them into the product.

Fedora L10N 執導委員會

The Fedora Localization Steering Committee (FLSCo) leads the Fedora Localization Project (FLP). Its mission is to provide the Fedora translators with necessary guidance, and support their efforts to localize the Fedora Project to multiple languages and cultures.

If you have a question, need clarifications or have problems, please contact Fedora L10n Steering Committee.

For more information: Fedora L10n Steering Committee

臭蟲回報、測試、品質保證等

Before you file a bug, please read through the list of current and previous bugs for the corresponding software package to determine if your bug has already been filed. If your bug does not exists, enter a bug report using the Bugzilla bug entry page. If your bug exists and has not been fixed, add additional information to the existing bug. If your bug exists and has been fixed, upgrade to the version in the bug report to determine if the bug was properly fixed. If it was not, reopen the bug.

Useful Bugzilla pages:

Some other interesting Bugzilla queries: