Activity Translations: Difference between revisions

From OLPC
Jump to navigation Jump to search
(add some specifics about what to include in a new request)
Line 31: Line 31:
== Translators ==
== Translators ==


* Refer to the [[Activities]] page to or directly to [http://translate.fedoraproject.org Fedora Translations] to find out the translation page for a certain activity.
* Go to page for the project you want to translate on [http://translate.fedoraproject.org Fedora Translations].
** [http://translate.fedoraproject.org/module/olpc-journal-activity Journal]
** [http://translate.fedoraproject.org/module/olpc-sugar Sugar]
** [http://translate.fedoraproject.org/module/olpc-web-activity Web]
** [http://translate.fedoraproject.org/module/olpc-write Write]
** [http://translate.fedoraproject.org/module/olpc-xbook Xbook]
* 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).
* 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 08:36, 28 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 for translators

  • 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

Get your strings localized

Once that's done the people who care about localization can get the .pot files to translate and can contribute them back.

Translators