Firefox 說明文件在地化

感謝您願意協助 Firefox 文件在地化的工作，全球數百萬說中文、看中文的 Firefox 使用者，都將因您的無私貢獻而受益。

需要您幫忙！

我們一直在尋找將文件在地化的人員. 請參閱 Site Credits, 這一頁可以了解是否已經有您的語言翻譯. 如果沒有的話，我們很樂意和你開始在地化的工作. 若您想進行正體中文 zh-TW 語系的翻譯，可以聯繫 dwchiang 或參考「MozTW 參與我們」的 SUMO 專案。

我想要成為在地化貢獻者，我應該做什麼？

首先，您可以聯繫 Rosana - 全球 SUMO 支援專案社群經理 - rardila (at) mozilla (dot) com，或是聯繫正體中文 MozTW 社群。 我們可以回答你的問題，並帶領你動手做，或帶領你與相同語系的其他貢獻者聯繫。如果你在這個語言清單 Site Credits 當中找的到你想協助貢獻的語言，你可以點選該語系領導者的名稱，寄給他或她一個訊息。並且你需要註冊一個 SUMO 帳號。

如何進行 SUMO 在地化？

SUMO 專案在地化工作分成兩個部分。第一個部分是使用者界面（按鈕，側邊欄的文字，等等。）請參閱 如何在地化SUMO的介面 看看如何動手協助這個部分。然後第二部分是說明文章的在地化，這些文章可以直接使用這個網站工具即可進行翻譯，這個網站本身就是一個方便進行翻譯與在地化的 Wiki。文件在地化的工作條列如下：

• 一般文章
  • 問題修正：遇到問題如何修正類型的文章
  • How to：說明如何使用某功能的文章

一般文章，都是給造訪者的完整知識庫文件。跟其他 wiki 一樣，為這些文章在地化將提供給使用者更棒的使用體驗。

• 非一般文章
  • 導覽：這些文件是特殊頁面，例如起始頁面 (startpages)，或問個問題 (Ask a question) 頁面。
  • 範本：文章的有些部分會重複地被使用在其他文章中，如果能夠共用這些共同內容段落然後插入到文件中，會非常有用。因此我們會使用「範本」。你可以在這裡找到所有的範本： 模板清單。
  • 如何貢獻(How to contribute)：這一頁有許多對貢獻者有幫助的文章。你不需要在地化他們，他們只會提供給有註冊成貢獻者的帳號，不會顯示在搜尋結果中。
  • 管理 (Administration)：其他不屬於上述類別的文章會歸於此類。

新手該怎麼上路？

先到 知識庫主控台 去看看，在本站的側邊欄也有連結可以通往該頁。知識庫主控台很重要，會是未來大部分在地化工作的起點，請仔細閱讀。

首先，可以試著翻譯一篇短文，了解流程

1. 前往知識庫主控台。
2. 最上方有最多瀏覽次數文章，點選第一篇還沒翻譯的文章，然後從該文章網頁側邊欄的 Editing Tools 標籤下，選擇 Translate Article，接著再點選目標語言。（正體中文 zh-TW 在頁面最下方附近。）
3. 往下一頁，英文原版會顯示在左邊，而翻譯的句子則放在右邊。從最上方開始，請先幫此頁取個名字，下面的 slug 自訂字串 則可保留原樣，或比照英文。
4. 接著請翻譯關鍵詞，讓網友比較容易找文章。
5. 然後，翻譯搜尋結果概要。這段文字會在站內搜尋時，於結果頁上顯示。
6. 終於要進入本文區了！除了在角括號（[ 跟 ]、{ 跟 } 都算）內的文字之外，請把每個句子都翻譯完。請留意產品界面標籤翻譯。如果你不確定某些東西代表什麼意思，可以閱讀How to use "For" tags及Using Templates了解更多資訊。
7. 完成後，將文章送出審核，也請記得留下簡要的翻譯摘要，這段摘要會留在文章的翻譯歷史紀錄裡。
8. 審核通過後您會收到一封電子郵件，所有人也就可以看到你的翻譯成果。這就是你第一篇 SUMO 文章，恭喜你了！

由於審核的人也是志工，可能一個星期左右才會「結清」一次，請給點耐心。若審核遲遲不過，可以傳站內私訊通知負責該語言的夥伴。

翻譯 slug 自訂字串

slug 自訂字串是文章網址 url 的一部份例如：http://support.mozilla.org/en-US/kb/this-is-the-slug 。It shouldn't exceed 50 characters. From the auto-generated slug, you can remove stop words and other unnecessary words. Make sure it stays human readable and has the most important information.

Translating keywords

An article must be easily findable. That's the role of keywords. All words in the title that are not English stop words such as "the" and "is" are already considered as keywords, so don't add them as keywords. Depending on your locale, translate some or all the keywords and eventually add synonyms, related terms, regional versions, usual typos, and usual anglicisms. DO NOT add too many keywords because each one of them will have less weight. For more info, see When and how to use keywords to improve an article's search ranking.

Translating the search summary

Try to find a compromise between an accurate translation and the 160-character max limit so that it's fully displayed in Google search results.

Translating product UI labels

The product UI is usually not translated by you. In order to know what is the chosen label, use the Transvision glossary.

How do I update articles after their first translation?

English articles are regularly updated with three levels of edits:

1. minor edit = Minor details that don't affect the instructions. These minor changes are not important for localizers and they will not be notified.
2. major edit/content change (default) = more than minor edit, but the change doesn’t diminish the value of the localized articles. Only localizers are notified by mail.
3. major edits/translation = This major edit changes the content of the article so much that the value of the localization is severely diminished. Localizers are notified about the change and the localized page get an "out of date" header, telling readers that the article is not up to date anymore.

Here are some tips to make the KB update easier.

How can I keep track of all the changes going on?

1. Go to your localization dashboard.
2. On the left side there is a text that says Email me when revisions are.... Click on it.
3. The menu presents you the following options:
   • Waiting for review: Anyone can submit articles. If you are a locale leader you should follow this category in your own language, so you can see when someone contributes to your locale.
     
   • Approved: Once an article is approved it's visible to the public. Again, follow this in your own language if you are a locale leader.
     
   • Ready for localization: Once an article is stable in the English version the editors will mark it as ready for localization. If you are a localizer you should follow this, so you will always be alerted of changes to the English KB.

Editing an article with a large diff

When an English article has many changes, the diff is large and it's hard to track which changes you've already taken into account in the localization editor. To ease this task, clone the editing page in a new window, put it at the right of the current page and scroll up to the diff. You will have the English source at the far left and the diff at the right.

Further information

Here are some more interesting links for you:

How to be a SUMO locale leader

You'll find the basic information on how to support and grow your locale here

Reviewer Guideline

Here you will get all the important information on how to be a reviewer at SUMO