Translation HOWTO

From Openmoko

Revision as of 19:52, 28 April 2007 by Cga (Talk | contribs)

Jump to: navigation, search

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 wiil fit also: vim, emax, 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

openmoko-dev maillist may be perfect place for all tlocalisators to meet, it also possible to tag email hesders with [i18n] for example.

this is a contradiction with the actual situation. please join the community ml for now. there's also some talking about creating a translator ml here and here: OM-i18n-ml (i just posted on the community mailinglist 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 wiil fit also: vim, emax, 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

openmoko-dev maillist may be perfect place for all tlocalisators to meet, it also possible to tag email hesders with [i18n] for example.

this is a contradiction with the actual situation. please join the community ml for now. there's also some talking about creating a translator ml here and here: OM-i18n-ml (i just posted on the community mailinglist 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