Activity Translations: Difference between revisions

From OLPC
Jump to navigation Jump to search
(New page: These instructions applies to a python activity using the base activity classes and the bundlebuilder. = Activity authors = == Make the code translatable == * Import the gettext module ...)
 
No edit summary
Line 1: Line 1:
These instructions applies to a python activity using the base activity classes and the bundlebuilder.
These instructions applies to a python activity using the base activity classes and the bundlebuilder.


= Activity authors =
== Activity authors ==


== Make the code translatable ==
=== Make the code translatable ===


* Import the gettext module
* Import the gettext module
Line 13: Line 13:
self._forward.set_tooltip(_('Forward'))
self._forward.set_tooltip(_('Forward'))


== Generate the POT file ==
=== Generate the POT file ===


* You will need to generate it and push it in the repository every time you add strings. (XXX how do we automatize it)
* You will need to generate it and push it in the repository every time you add strings. (XXX how do we automatize it)


./setup.py dist
./setup.py dist

== Translators ==

* Refer to the [Activities] page to or directly to [Fedora Translations http://dev.laptop.org/git.do?p=web-activity;a=tree] to find out the translation page for a certain activity.
* Once your translation is ready open a new [Trac ticket http://dev.laptop.org/newticket], in the Localization component and attach your translation (as a .po file).

Revision as of 16:18, 21 June 2007

These instructions applies to a python activity using the base activity classes and the bundlebuilder.

Activity authors

Make the code translatable

  • Import the gettext module
from gettext import gettext as _
  • Mark strings as translatable using _('String')
self._forward.set_tooltip(_('Forward'))

Generate the POT file

  • You will need to generate it and push it in the repository every time you add strings. (XXX how do we automatize it)
./setup.py dist

Translators