Activity Translations: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(make a link to the localization background page)
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. For more background information about Localization please see the [[Localization]] page.


== Activity authors ==
== Activity authors ==

Revision as of 17:23, 21 June 2007

These instructions applies to a python activity using the base activity classes and the bundlebuilder. For more background information about Localization please see the Localization page.

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

Add your module to Fedora Translations

  • Open a new Trac ticket, in the Localization component, specifying the source repository location.

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).