Translation Workflow: Difference between revisions

From KDE UserBase Wiki
mNo edit summary
(Merge guide line section.)
 
(53 intermediate revisions by 15 users not shown)
Line 1: Line 1:
This page attempts to define the workflow for migration to the new translation system and for using the new system.
<languages />
<translate>


==Migration==
<!--T:36-->
===Tasks and notes for English-speaking Editors===
{{Remember|1=This page is obsolete. For information on translation see [[Special:myLanguage/Tasks_and_Tools#Working_with_Languages|Working with Languages]] and links in that section.}}
:* Urgently required - On all pages, an empty line should follow headings and sub-headings.  This should be checked before the markup discussed next is added.
:* Smilies cause problems for translators.  Please replace any with <nowiki>[[Image:Face-smile.png]]</nowiki>[[Image:Face-smile.png]]
:* Any image that is referenced as <nowiki>[[File:somename.png]]</nowiki> should be changed to the more specific <nowiki>[[Image:somename.png]]</nowiki>
:* Check that the page has a Category statement as in
:: <nowiki>[[Category:System]]</nowiki>
:* When editing of a page is complete, one of the Administration group will add
<nowiki>
  &lt; languages / &gt;
  &lt; translate &gt;
</nowiki>
:::to the top of the page, and <nowiki> &lt; /translate &gt;</nowiki> at the bottom.  There should be no spaces inside the angle-brackets.


:::It is no longer possible for other contributors to tag a page for translation.  This is because pages were being marked for translation far faster than translators could handle.
<!--T:1-->
Much 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 [[Special:myLanguage/Tasks_and_Tools|Tasks and Tools]].


:* Markup should generally be excluded from tagging.  This is achieved by the use of multiple <translate></translate> tags, for example:
<!--T:2-->
<pre style="margin-left: 4em"><nowiki>
{{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.}}
|<imagemap>
&lt;translate>Image:Okular.png&lt;/translate>|48px
default &lt;translate>[[Okular|Okular]]&lt;/translate>
desc none
</imagemap>||'''&lt;translate>[[Okular|Okular]]&lt;/translate>'''
:&lt;translate>KDE's universal document viewer.&lt;/translate>
</nowiki></pre>


:* Any page that is seen to be seriously and hopelessly out of date should not be marked for translation during the migration period.  Those pages can be translated afresh at the later stage.
== Guidelines applicable to all Languages == <!--T:3-->
:* Where images are seen to be out of date, they should be amended before marking for translation.
:* Pages with 'Manual' in the title will be re-marked for translation when the author tells us that it has significant changes for a newer version.
:* Pages that are known to be 'hot topics' of the moment should be prepared first, as they are the ones most likely to be visited in the short term. 
:* When marking a page for translation, the old-style language bar should not be included and
:* The Category marking should be included
:*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 rewrite a section, in which case you should 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.


===Tasks and notes for Translators===
<!--T:4-->
:* ''You must request that your user account is added to the group of Translators.  Only listed Translators, logged in, can see the prompts and create translations.''
{{Info|This section is new, and will be controlled by experienced translators.}}
:* Ensure that a table of Category translated words for your language exists.  You can check using the links on http://userbase.kde.org/Translation_Help_Needed
:* During the migration period it is expected that we will need to keep the old language-bar as well as showing the new one.  This will inevitably look a little messy, so we'll keep the period as short as possible.  The idea is that you, or anyone with enough understanding of the language to recognise what is being said, can access the old version and simply copy/paste the relevant sections into the new translation page.
:* Pages to be worked on should be prioritised.  
::* Group 1 - pages relating to the current 'hot topics':
::::Akonadi
::::Akonadi 4.4/Troubleshooting
::::KAddressbook
::::Akonadi and AddressBook


::* Group 2 - pages most immediately needed by newcomers:
::::Welcome to KDE UserBase
::::Quick_Start
::::Getting_Help
::::Glossary
::::UserBase
::::What is KDE


:::Please concentrate on these pages first and let us know on #kde-www when you are satisfied with your language translation of those pages.
===KDE style=== <!--T:5-->
:* Some pages were translated very early on in the life-cycle of KDE 4.x and never updated.  It's probably best to ignore these for the first run through, so we will not mark such pages as ready for translation.
:* If you are fluent in languages other than English, you can take advantage of translations in those languages (if any), by going into your preferences and adding those languages to your list under section Editing.
:* The final line of a page will normally be a Category statement.  Please leave the word Category untranslated, and translate the category name according to the  tables listed on [[Translation_Help_Needed]]


==Using the new Translate extension - on-line Translation==
<!--T:6-->
:# An English-speaking editor marks the page as ready for translation.
The KDE voice is helpful, aspirational, and genuine. Our communications strive to be:
:# A logged-in Translator sees "Translate this page" at the top of the page.
:# Clicking on that link takes you to a page, Special:Translate, where you can choose whether to view every section or untranslated sections relating to the page.  This is useful if you need to do it in consecutive sessions.
:## You then need to select your language from the drop-down list.
:## Clicking on the first blue link begins the translation process.  If you have JavaScript enabled, you will see a dialog that allows you translate each section on at a time.
:## If JavaScript is not enabled or does not work, the first link will go to normal edit page, with some extra features like the source text to translate. You can speed the process by opening multiple pages to browser tabs.
:# When you have finished, or run out of time for the current session, return to the page with list of sections either by closing the translation dialog or selecting "Return to List" from translation page.  You can then use the link above the section list to return to the English page.  Your language code will have been added to the list of translations for the page.


==Using the new Translate extension - off-line Translation==
<!--T:7-->
:* The Translate extension offers the possibility of exporting to a .po file which can be used by tools such as Lokalize.  If you choose to do it this way, please be aware of the possibility of someone else working on the same page.  Unless we come up with a better solution, I'd suggest that we get a template rather like the <nowiki>{{Being_Edited}}</nowiki> one.  We have yet to experiment with how this can be achieved, since the page is not created until you actually start the first translation of a page.
;Efficient
:* You can download the po file by choosing "export in Gettext format" task in the page with list of translatable sections.
:Highlight the elegance of efficiency — from steps removed and labor reduced to costs saved.
:* To import translations you need to have right XYZ, and then you can go to Speical:ImportTranslations and follow the instructions.  We are still working on this part of the process.


At almost all times there will be someone on irc.freenode.net, #kde-www, who can answer questions.
<!--T:8-->
;Effortless
: Communicate in intrinsically simple terms. Be concise, intuitive, eloquent, and fluid.


''It's inevitable that we will find glitches at first. The developers are working with us to fix them.  Meanwhile, please watch the Discussion page attached to this page, so that you are aware of issues.''
<!--T:9-->
;Useful
: Address real needs and open up new opportunities.


<!--T:10-->
;Immersive
: Make communications as engaging and comprehensive as the technology they cover.
<!--T:11-->
;Meaningful
: Use real examples and genuine recommendations to make the message personal and relevant.
===Know Your Skills=== <!--T:12-->
<!--T:13-->
KDE relies on volunteer translators to help make useful KDE information available around the world.
As volunteers, you are not required to have any formal language training, but we do ask that you know your fluency and get the support you need to finish a translation if you run into tricky language issues or content that lies outside your translation capabilities.
<!--T:14-->
Because many of the articles on KDE wiki are technical in nature, it also helps to be familiar with—and even fluent in—KDE products.
You will need to be able to distinguish between common terms and technical terms in context and determine when user interface or workflow elements that are mentioned in the articles need to be translated.
===General guidelines=== <!--T:15-->
<!--T:16-->
;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.
<!--T:17-->
;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.
<!--T:18-->
;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].
: 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:19-->
;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.
<!--T:20-->
;Units of measurement
: Convert units of measure to make them relevant for the intended language or region. For example, some English-speaking countries use the unit of inch, but other countries may prefer centimeter unit.
<!--T:21-->
;User interface terms
: Translate user interface terms as appropriate for your language.
<!--T:22-->
See here for more information:
<!--T:23-->
1. http://translate.sourceforge.net/wiki/guide/start
<!--T:24-->
2. Glossary: http://translate.sourceforge.net/wiki/guide/glossary
<!--T:25-->
3. Another Glossary: http://www.glossary.com/category.php?q=Computer
==Keeping up to date with developments== <!--T:28-->
<!--T:29-->
I propose that the Discussion page attached to this page should be used for orderly debate about issues noted, particularly issues where existing markup is causing problems.  Old threads, long since resolved will be cleaned out, and once decisions are made I will update the relevant help pages.  I would ask you to put a Watch on [[Talk:Translation_Workflow]].
==Getting a Better Understanding of the Process== <!--T:30-->
For a fuller description of the Translate extension, read the description on [http://translatewiki.net/wiki/Translating:Page_translation_feature the developers' website]
<!--T:31-->
{{Tip|1=Monitor the status of your language statistics by monitoring the page  [[Special:LanguageStats]] if you have your own language set as the interface language of UserBase.}}
</translate><span id="Language-specific guideline pages"></span><translate>
==Language-specific guideline pages == <!--T:32-->
<!--T:35-->
{{Tip|2=All Right-to-Left script Languages|1=Mediawiki is not yet good at supporting RTL languages.  Currently, the workaround is to add <code>< div dir="rtl" ></code> at the start of your translation (i.e. in the first message) and <code>< /div ></code> after the final category statement}}
<!--T:27-->
We propose to have Team Leaders for each language.  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 are listed below:
<!--T:33-->
:[[Translation_Workflow/Catalan|Catalan]]
:[[Translation_Workflow/Chinese|Chinese]]
:[[Translation_Workflow/Danish|Danish]]
:[[Translation_Workflow/French|French]]
:[[Translation_Workflow/Galician|Galician]]
:[[Translation_Workflow/German|German]]
:[[Translation_Workflow/Italian|Italian]]
:[[Translation_Workflow/Romanian|Romanian]]
:[[Translation_Workflow/Russian|Russian]]
:[[Translation_Workflow/Spanish|Spanish]]
:[[Translation_Workflow/Ukrainian|Ukrainian]]
<!--T:34-->
[[Category:Admin]]
[[Category:Admin]]
</translate>

Latest revision as of 08:58, 22 March 2013

Other languages:

Remember

This page is obsolete. For information on translation see Working with Languages and links in that section.


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

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.


Guidelines applicable to all Languages

Information

This section is new, and will be controlled by experienced translators.


KDE style

The KDE voice is helpful, aspirational, and genuine. Our communications strive to be:

Efficient
Highlight the elegance of efficiency — from steps removed and labor reduced to costs saved.
Effortless
Communicate in intrinsically simple terms. Be concise, intuitive, eloquent, and fluid.
Useful
Address real needs and open up new opportunities.
Immersive
Make communications as engaging and comprehensive as the technology they cover.
Meaningful
Use real examples and genuine recommendations to make the message personal and relevant.

Know Your Skills

KDE relies on volunteer translators to help make useful KDE information available around the world. As volunteers, you are not required to have any formal language training, but we do ask that you know your fluency and get the support you need to finish a translation if you run into tricky language issues or content that lies outside your translation capabilities.

Because many of the articles on KDE wiki are technical in nature, it also helps to be familiar with—and even fluent in—KDE products. You will need to be able to distinguish between common terms and technical terms in context and determine when user interface or workflow elements that are mentioned in the articles need to be translated.


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 measurement
Convert units of measure to make them relevant for the intended language or region. For example, some English-speaking countries use the unit of inch, but other countries may prefer centimeter unit.
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

Keeping up to date with developments

I propose that the Discussion page attached to this page should be used for orderly debate about issues noted, particularly issues where existing markup is causing problems. Old threads, long since resolved will be cleaned out, and once decisions are made I will update the relevant help pages. 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 Special:LanguageStats if you have your own language set as the interface language of UserBase.

Language-specific guideline pages

All Right-to-Left script Languages

Mediawiki is not yet good at supporting RTL languages. Currently, the workaround is to add < div dir="rtl" > at the start of your translation (i.e. in the first message) and < /div > after the final category statement


We propose to have Team Leaders for each language. 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 are listed below:

Catalan
Chinese
Danish
French
Galician
German
Italian
Romanian
Russian
Spanish
Ukrainian
Retrieved from "https://userbase.kde.org/index.php?title=Translation_Workflow&oldid=301562"