Difference between revisions of "Translation Workflow"

Jump to: navigation, search
 
(12 intermediate revisions by 5 users not shown)
Line 2: Line 2:
 
<translate>
 
<translate>
  
 +
<!--T:1-->
 
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|Tasks and Tools]].   
 
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|Tasks and Tools]].   
  
{{Warning|1=When editing pages that are already marked for translation, you will see section markers similar to </translate><nowiki><!--T:1--></nowiki>. <translate>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.}}
+
<!--T:2-->
 +
{{Warning|1=When editing pages that are already marked for translation, you will see section markers similar to <nowiki>< !--T:1-- ></nowiki>. 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.}}
  
=== General guidelines ===
+
=== General guidelines === <!--T:4-->
  
 +
<!--T:5-->
 
;Expressions, jargon, and humor
 
;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.  
 
: 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.
 
: 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.
  
 +
<!--T:6-->
 
;Proper names
 
;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.  
 
: 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.
 
: People's names should remain in English for Latin-based languages, but you may transliterate them for non-Latinbased alphabets.
  
 +
<!--T:7-->
 
;Terminology
 
;Terminology
 
: For help with translating tricky constructions or technical terms, consult the translation-sharing site to: [http://www.tausdata.org/index.php/taus-search TAUS].  
 
: For help with translating tricky constructions or technical terms, consult the translation-sharing site to: [http://www.tausdata.org/index.php/taus-search 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.  
 
: 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.  
  
 +
<!--T:8-->
 
;Titles of works
 
;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.  
 
: 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.  
 
: If you cannot find a translation for that particular title in your language, do your best to translate it as accurately as possible.  
  
 +
<!--T:9-->
 
;Units of measure
 
;Units of measure
 
: Convert units of measure to make them relevant for the intended language or region.
 
: Convert units of measure to make them relevant for the intended language or region.
  
 +
<!--T:10-->
 
;User interface terms
 
;User interface terms
 
: Translate user interface terms as appropriate for your language.
 
: Translate user interface terms as appropriate for your language.
  
  
 +
<!--T:11-->
 
See here for more information:
 
See here for more information:
  
 +
<!--T:12-->
 
1. http://translate.sourceforge.net/wiki/guide/start
 
1. http://translate.sourceforge.net/wiki/guide/start
  
 +
<!--T:13-->
 
2. Glossary: http://translate.sourceforge.net/wiki/guide/glossary
 
2. Glossary: http://translate.sourceforge.net/wiki/guide/glossary
  
 +
<!--T:14-->
 
3. Another Glossary: http://www.glossary.com/category.php?q=Computer
 
3. Another Glossary: http://www.glossary.com/category.php?q=Computer
  
== Guidelines specific to a Language ==
+
== Guidelines specific to a Language == <!--T:15-->
  
 +
<!--T:16-->
 
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]].
  
== Keeping up to date with development ==
+
== Keeping up to date with development == <!--T:17-->
  
 +
<!--T:18-->
 
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]].
 
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 ==
+
== Getting a Better Understanding of the Process == <!--T:19-->
  
 +
<!--T:20-->
 
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]
  
 +
<!--T:21-->
 
{{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.}}
 
{{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 == <!--T:22-->
  
 +
<!--T:23-->
 
Volunteer Team Leaders, please link your page from here (or ask for help)
 
Volunteer Team Leaders, please link your page from here (or ask for help)
  
 +
<!--T:25-->
 +
:[[Translation_Workflow/French|French]]
 +
:[[Translation_Workflow/Italian|Italian]]
 +
:[[Translation_Workflow/fi|Finnish]]
 +
:[[Translation_Workflow/zh-tw|Traditional Chinese]]
 +
 +
<!--T:24-->
 
[[Category:Translator_Help]]
 
[[Category:Translator_Help]]
 
</translate>
 
</translate>

Latest revision as of 10:22, 20 July 2013

Other languages:Czech 24% • ‎Greek 46% • ‎English 100% • ‎Spanish 90% • ‎Finnish 98% • ‎French 4% • ‎Japanese 42% • ‎Brazilian Portuguese 98% • ‎Slovak 4% • ‎Chinese (China) 12% • ‎Chinese (Taiwan) 98%

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

[edit] General guidelines

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

[edit] 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.

[edit] 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.

[edit] 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.


[edit] Language-specific guideline pages

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

French
Italian
Finnish
Traditional Chinese

This page was last modified on 20 July 2013, at 10:22. This page has been accessed 9,686 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal