Translation Workflow/zh-tw: Difference between revisions
(Importing a new version from external source) |
(Importing a new version from external source) |
||
| Line 38: | Line 38: | ||
3. 另一個詞彙表：http://www.glossary.com/category.php?q=Computer | 3. 另一個詞彙表：http://www.glossary.com/category.php?q=Computer | ||
== | == 跟語言相關的指引 == | ||
UserBase proposes to have Team Leaders for each language. Techbase may, at a later date, do the same. As we get leaders appointed, they will take charge of a page of guidelines for their specific language, where they will be named. They will have final say on any question relating to their language. The guidelines will be linked from [[Translation_Workflow#Language-specific_guideline_pages|Language-specific guideline pages]]. | UserBase proposes to have Team Leaders for each language. Techbase may, at a later date, do the same. As we get leaders appointed, they will take charge of a page of guidelines for their specific language, where they will be named. They will have final say on any question relating to their language. The guidelines will be linked from [[Translation_Workflow#Language-specific_guideline_pages|Language-specific guideline pages]]. | ||
Revision as of 09:18, 20 July 2013
目前這個頁面上的某些資訊已經過時。所有的貢獻者相關的工作，包括線上與離線翻譯，都有 HOWTO 可以參考，您也可以在 工作與工具頁面中找到相關連結。
一般指引
- 表達、行話與幽默
- 在您翻譯的時候，您可能會遇到一些在原始語言中才會出現的表達方式，雙關語，或是行話甚至黑話，不知道該怎麼翻譯才對。
- 在這種狀況下，您不需要逐字翻譯，只要試著將文章的觀念與重點表達出來即可。小心地瞭解整段訊息的意思，不必擔心失去原文中的幽默感或是口語用法。
- 適當的名稱
- 公司名稱與產品名稱不太需要翻譯，通常最好保留英文，除非是在您的所在地也有大家耳熟能詳的名稱。
- 人名也盡可能保留原文。
- 專業術語
- 若是您翻譯一些技術名詞或是一些難以解釋的意義時，您可以參考這個翻譯分享站台：TAUS。
- 只要將您要翻譯的文字輸入並選擇翻譯的來源與目標語言。當然不是所有的語詞都能翻譯成任意語言，不過相信這個工具能對您的精確翻譯有相當的幫助。
- 標題
- 當您寫到一本書、程式、功能、系統套件或其他公開的成果時，您可以看看它們有沒有由作者或發布者正式翻譯過的名字。如果有，就直接使用該翻譯。
- 如果沒有，就盡可能的準確地翻譯吧。
- 測量單位
- 將測量單位轉換成您的區域常用的單位。
- 使用者介面語詞
- 將使用者介面的語詞翻譯成您的語言。
更多資訊可以參考這裡：
1. http://translate.sourceforge.net/wiki/guide/start
2. 詞彙表：http://translate.sourceforge.net/wiki/guide/glossary
3. 另一個詞彙表：http://www.glossary.com/category.php?q=Computer
跟語言相關的指引
UserBase proposes to have Team Leaders for each language. Techbase may, at a later date, do the same. As we get leaders appointed, they will take charge of a page of guidelines for their specific language, where they will be named. They will have final say on any question relating to their language. The guidelines will be linked from Language-specific guideline pages.
Keeping up to date with development
I propose that the Discussion page attached to this page should be used for orderly debate about general issues noted, particularly issues where existing markup is causing problems. I would ask you to put a Watch on Talk:Translation_Workflow.
Getting a Better Understanding of the Process
For a fuller description of the Translate extension, read the description on the developers' website
Language-specific guideline pages
Volunteer Team Leaders, please link your page from here (or ask for help)