Translation Workflow/zh-tw: Difference between revisions

Revision as of 09:18, 20 July 2013

Other languages:

目前這個頁面上的某些資訊已經過時。所有的貢獻者相關的工作，包括線上與離線翻譯，都有 HOWTO 可以參考，您也可以在工作與工具頁面中找到相關連結。

Template:警告

一般指引

表達、行話與幽默: 在您翻譯的時候，您可能會遇到一些在原始語言中才會出現的表達方式，雙關語，或是行話甚至黑話，不知道該怎麼翻譯才對。; 在這種狀況下，您不需要逐字翻譯，只要試著將文章的觀念與重點表達出來即可。小心地瞭解整段訊息的意思，不必擔心失去原文中的幽默感或是口語用法。

Proper names: Company names and product names should never be translated. Proper company names and product names should always remain in English, no matter what language you are translating for.; People's names should remain in English for Latin-based languages, but you may transliterate them for non-Latinbased alphabets.

Terminology: For help with translating tricky constructions or technical terms, consult the translation-sharing site to: TAUS.; Simply enter your desired text and then choose which language to translate it from and to. Not all terms are included for all languages, but this can be a helpful tool for completing accurate translations.

Titles of works: When you run across the title of a book, program, feature, distro, or other public work, check to see if that title has already been officially translated for your language (by the publisher or distributor), and if so, use that translation.; If you cannot find a translation for that particular title in your language, do your best to translate it as accurately as possible.

Units of measure: Convert units of measure to make them relevant for the intended language or region.

User interface terms: Translate user interface terms as appropriate for your language.

See here for more information:

1. http://translate.sourceforge.net/wiki/guide/start

2. Glossary: http://translate.sourceforge.net/wiki/guide/glossary

3. Another Glossary: http://www.glossary.com/category.php?q=Computer

Guidelines specific to a Language

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

Tip

Monitor the status of your language statistics by monitoring the page http://techbase.kde.org//your-language-code or simply Special:LanguageStats if you have your own language set as the interface language of TechBase.

Language-specific guideline pages

Volunteer Team Leaders, please link your page from here (or ask for help)

French

Italian

Finnish

@@ Line 7: / Line 7: @@
 === 一般指引 ===
-;Expressions, jargon, and humor
+;表達、行話與幽默
-: As you translate, you may encounter expressions, puns, or jargon that are specific to the original language and may be difficult to translate effectively.
+: 在您翻譯的時候，您可能會遇到一些在原始語言中才會出現的表達方式，雙關語，或是行話甚至黑話，不知道該怎麼翻譯才對。
-: In such cases, translate the concept or point the article is trying to convey and not the exact words. : Take care to ensure you capture the overall message, and don't worry about losing the humor or the colloquialism.
+: 在這種狀況下，您不需要逐字翻譯，只要試著將文章的觀念與重點表達出來即可。小心地瞭解整段訊息的意思，不必擔心失去原文中的幽默感或是口語用法。
 ;Proper names