Translation HOWTO

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(Article title and category naming guidelines.)
m (Translating Openmoko Wiki: format)
Line 7: Line 7:
 
Rule of thumb: It's better to have some translation than nothing, so feel free to translate.
 
Rule of thumb: It's better to have some translation than nothing, so feel free to translate.
  
=== Translated article titles ===
+
To create a new translation, simply click on your language's link when viewing the English version and start editing in the appearing box.
 
+
Please use the '''English''' title of the article. This will ensure that the language bar template can link to localized version of the article. For example: [[Main_Page]] and [[Main_Page/fr]].
+
 
+
To create a new translation, simply add your language's code after the page name when viewing the English version and start editing in the appearing box.
+
  
 
Always add the Languages template to the page, so that users can link back to other languages. For example this page starts with:
 
Always add the Languages template to the page, so that users can link back to other languages. For example this page starts with:
Line 21: Line 17:
 
Translated articles should not be added to the English category. Please always use the language suffix for the category name too.
 
Translated articles should not be added to the English category. Please always use the language suffix for the category name too.
  
=== Translated category names ===
+
=== Article titles ===
 +
 
 +
Please use the '''English''' title of the article. This will ensure that the language bar template can link to localized version of the article. For example: [[Main_Page]] and [[Main_Page/fr]].
 +
 
 +
=== Category names and category pages ===
  
The category names must be '''English''', and append your language's code to the end. This will ensure that language bar will work and allow users to navigate between various languages. For example: [[:Category:Hardware]] and [[:Category:Hardware/fr]].
+
The category names must be '''English'''. Append your language's code to the end. This will ensure that language bar will work and allow users to navigate between various languages of the category. For example: [[:Category:Hardware]] and [[:Category:Hardware/fr]].
  
If the category name becomes red in your article, that means there is no '''category page''' for this category yet in this lagnuage. (First make sure you don't have a typo in the name!) Please click that red category name, and create the category page for it, which contains the following:
+
If the category name becomes red in your article, that means there is no '''category page''' for this category yet in this language. (First make sure you don't have a typo in the name!) Please click that red category name, and create the category page for it, which contains the following:
  
 
* Languages template, same as on the English version of the category
 
* Languages template, same as on the English version of the category
 
* Parent categories, same as on the English version but with language suffixes
 
* Parent categories, same as on the English version but with language suffixes
  
For example:
+
For example on [[:Category:Basic End User]]:
  
 
<pre><nowiki>
 
<pre><nowiki>

Revision as of 12:39, 31 August 2008


Main page for localization is Translation. This page contains some help on how to do Wiki text and Openmoko software translations.

Contents

Translating Openmoko Wiki

Rule of thumb: It's better to have some translation than nothing, so feel free to translate.

To create a new translation, simply click on your language's link when viewing the English version and start editing in the appearing box.

Always add the Languages template to the page, so that users can link back to other languages. For example this page starts with:

{{Languages|Translation_HOWTO}}

Translated articles should not be added to the English category. Please always use the language suffix for the category name too.

Article titles

Please use the English title of the article. This will ensure that the language bar template can link to localized version of the article. For example: Main_Page and Main_Page/fr.

Category names and category pages

The category names must be English. Append your language's code to the end. This will ensure that language bar will work and allow users to navigate between various languages of the category. For example: Category:Hardware and Category:Hardware/fr.

If the category name becomes red in your article, that means there is no category page for this category yet in this language. (First make sure you don't have a typo in the name!) Please click that red category name, and create the category page for it, which contains the following:

  • Languages template, same as on the English version of the category
  • Parent categories, same as on the English version but with language suffixes

For example on Category:Basic End User:

{{Languages|:Category:Basic End User}}

[[Category:Community/de]]

Of course you may want to translate the English description of this category too and add between these lines.

Finding what to translate

If you are not sure what page is most popular and ready for translation. Please refer to following list.

Please start at these pages. Or you can add the page you think is important.

Page Name Language Versions Maintainer Status
Getting Started with your Neo FreeRunner Tranditional Chinese coolcat (talk · contribs) Finished
Neo FreeRunner GTA02 Hardware Tranditional Chinese coolcat (talk · contribs) Finished
Booting from SD Tranditional Chinese coolcat (talk · contribs) Finished
Toolchain Tranditional Chinese coolcat (talk · contribs) Finished
Distributions none none todo
Om2008.8 none none todo

Translating Openmoko software

There are specialized tools for *.pot (*.po) files edition gtranslator, po4a, poedit, pootle, potool ... Pootle can host several projects and languages to coordinate translation activities, and allow online translation.

Most of text editors will fit also: vim, emacs, ed, gedit ...

Updating source tree

TODO: descript SVN update after editing (See: To-Do List)

Notes

  • Encoding for *.po is UTF-8
  • Most of packages in OpenEmbedded tree already internationalized, its worth to review them

Common space for localization effort

please join the community ml for now. there's also some talking about creating a translators ml here and here: OM-i18n-ml feel free to join both discussions. cga sat apr 28th 20:48:35 CEST 2007)

List of Openmoko related PO's

Most of apps in /home/moko/sources/svn/ and /home/moko/openmoko/trunk/src/target/OM-2007/applications/ don have *.pot files for now, but some of them have *.po files for some of the languages

Personal tools


Main page for localization is Translation. This page contains some help on how to do Wiki text and Openmoko software translations.

Translating Openmoko Wiki

Rule of thumb: It's better to have some translation than nothing, so feel free to translate.

Translated article titles

Please use the English title of the article. This will ensure that the language bar template can link to localized version of the article. For example: Main_Page and Main_Page/fr.

To create a new translation, simply add your language's code after the page name when viewing the English version and start editing in the appearing box.

Always add the Languages template to the page, so that users can link back to other languages. For example this page starts with:

{{Languages|Translation_HOWTO}}

Translated articles should not be added to the English category. Please always use the language suffix for the category name too.

Translated category names

The category names must be English, and append your language's code to the end. This will ensure that language bar will work and allow users to navigate between various languages. For example: Category:Hardware and Category:Hardware/fr.

If the category name becomes red in your article, that means there is no category page for this category yet in this lagnuage. (First make sure you don't have a typo in the name!) Please click that red category name, and create the category page for it, which contains the following:

  • Languages template, same as on the English version of the category
  • Parent categories, same as on the English version but with language suffixes

For example:

{{Languages|:Category:Basic End User}}

[[Category:Community/de]]

Of course you may want to translate the English description of this category too and add between these lines.

Finding what to translate

If you are not sure what page is most popular and ready for translation. Please refer to following list.

Please start at these pages. Or you can add the page you think is important.

Page Name Language Versions Maintainer Status
Getting Started with your Neo FreeRunner Tranditional Chinese coolcat (talk · contribs) Finished
Neo FreeRunner GTA02 Hardware Tranditional Chinese coolcat (talk · contribs) Finished
Booting from SD Tranditional Chinese coolcat (talk · contribs) Finished
Toolchain Tranditional Chinese coolcat (talk · contribs) Finished
Distributions none none todo
Om2008.8 none none todo

Translating Openmoko software

There are specialized tools for *.pot (*.po) files edition gtranslator, po4a, poedit, pootle, potool ... Pootle can host several projects and languages to coordinate translation activities, and allow online translation.

Most of text editors will fit also: vim, emacs, ed, gedit ...

Updating source tree

TODO: descript SVN update after editing (See: To-Do List)

Notes

  • Encoding for *.po is UTF-8
  • Most of packages in OpenEmbedded tree already internationalized, its worth to review them

Common space for localization effort

please join the community ml for now. there's also some talking about creating a translators ml here and here: OM-i18n-ml feel free to join both discussions. cga sat apr 28th 20:48:35 CEST 2007)

List of Openmoko related PO's

Most of apps in /home/moko/sources/svn/ and /home/moko/openmoko/trunk/src/target/OM-2007/applications/ don have *.pot files for now, but some of them have *.po files for some of the languages