Difference between revisions of "Translation Workflow"

Jump to: navigation, search
(Created page with "Some of the information that was on this page is now outdated. How-Tos exist for all the common contributor tasks, including translation, both on- and off-line, and can be found...")
 
Line 48: Line 48:
 
For a fuller description of the Translate extension, read the description on [http://translatewiki.net/wiki/Translating:Page_translation_feature the developers' website]
 
For a fuller description of the Translate extension, read the description on [http://translatewiki.net/wiki/Translating:Page_translation_feature the developers' website]
  
{{Tip|1=Monitor the status of your language statistics by monitoring the page http://userbase.kde.org//your-language-code or simply [[Special:LanguageStats]] if you have your own language set as the interface language of UserBaser.}}
+
{{Tip|1=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 ==
 
==Language-specific guideline pages ==

Revision as of 13:56, 5 July 2011

Some of the information that was on this page is now outdated. How-Tos exist for all the common contributor tasks, including translation, both on- and off-line, and can be found linked from Tasks and Tools.

noframe
 
Warning
When editing pages that are already marked for translation, you will see section markers similar to <!--T:1-->. Usually each paragraph is one section. You should not change the markers, unless you fully delete a section, in which case you should simply remove the old marker. When adding new sections, you don't need to add marker to it – the marker will be added automatically when your changes are approved for translation. If you want to move a section, move also the section marker with it. That is the only time when you touch the markers - the system will do the rest.


Contents

General guideline

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

Ktip.png
 
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)


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal
http://techbase.kde.org/index.php?title=Translation_Workflow&diff=61929&oldid=61882
techbase.kde.org
crawl=CC-MAIN-2013-20
38032
application/http; msgtype=response
sha1:3P4TEXOX62A44IUEIRAKS36MNH7C3MRL
<urn:uuid:623d9088-c3ca-48d0-9f89-0e6e9cfd7e99>
2013-06-20T09:03:52Z
199.83.128.99
sha1:3KEHTXCQX56NOKJLOHILQMWGPPIRGDZJ
<urn:uuid:8a2807f9-ddf8-4961-973a-e59845f66a28>
http://techbase.kde.org/index.php?title=Translation_Workflow&diff=61929&oldid=61882
response
<urn:uuid:e43c3f0d-6cbe-4385-9902-9ee8f485de5b>
robots: classic
hostname: ip-10-60-113-184.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2013-20
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for Spring 2013
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf