Translation HOWTO

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m (Software)
m (Common space for localisation effort)
Line 19: Line 19:
 
* Most of packages in Openembedded tree allready iternationalised, its worth to review them
 
* Most of packages in Openembedded tree allready iternationalised, its worth to review them
 
== Common space for localisation effort ==
 
== Common space for localisation effort ==
'''please join the community ml for now.''' there's also some talking about creating a translators ml [http://wiki.openmoko.org/wiki/Talk:Translation#Need_for_translation_mailing_list_.28and_coordinators.3F.29 here] [http://lists.openmoko.org/pipermail/community/2007-April/004973.html and here: OM-i18n-ml] feel free to join both discussions. [[User:Cga|cga]] sat apr 28th 20:48:35 CEST 2007)
+
'''please join the community ml for now.''' there's also some talking about creating a translators ml [[Talk:Translation#Need for translation mailing list (and coordinators?)|here]] [http://lists.openmoko.org/pipermail/community/2007-April/004973.html and here: OM-i18n-ml] feel free to join both discussions. [[User:Cga|cga]] sat apr 28th 20:48:35 CEST 2007)
  
 
== List of OpenMoko related PO's==
 
== List of OpenMoko related PO's==

Revision as of 13:20, 30 August 2007

Main page for localisation is Translation help to improve this page

Contents

Finding what to translate

First of all package creator/maintainer have to create *.pot file with all messages included. Search for this files in source tree and you can edit them.

Translating

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

Software

There are specialised tools for *.pot (*.po) files edition gtranslator, po4a, poedit, pootle, potool ...

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

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 allready iternationalised, its worth to review them

Common space for localisation 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 localisation is Translation help to improve this page

Finding what to translate

First of all package creator/maintainer have to create *.pot file with all messages included. Search for this files in source tree and you can edit them.

Translating

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

Software

There are specialised tools for *.pot (*.po) files edition gtranslator, po4a, poedit, pootle, potool ...

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

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 allready iternationalised, its worth to review them

Common space for localisation 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