Activity Translations: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
Line 21: Line 21:
== Translators ==
== 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.
* Refer to the [[Activities]] page to or directly to [http://dev.laptop.org/git.do?p=web-activity;a=tree Fedora Translations] 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).
* Once your translation is ready open a new [http://dev.laptop.org/newticket Trac ticket], in the Localization component and attach your translation (as a .po file).

Revision as of 16:20, 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

  • Refer to the Activities page to or directly to Fedora Translations to find out the translation page for a certain activity.
  • Once your translation is ready open a new Trac ticket, in the Localization component and attach your translation (as a .po file).