Activity Translations
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.
Contents
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
- Open a new Trac ticket, in the Localization component, specifying the source repository location. You will need to include the following information (with examples):
- Module name (Write)
- Maintainer Name + Email (Foo Bar / foo@foo.com)
- Maintainer URL (http://fedoraproject.org/wiki/ChristopherBlizzard)
- URL to your repository (i.e. http://dev.laptop.org/git.do?p=sugar;a=summary)
Once that's done the people who care about localization can get the .pot files to translate and can contribute them back.
Translators
- Go to the OLPC release set on Fedora Translations to find out which projects needs translation and to download the current translation files (or the POT).
- Please check if the translation hasn't been filed querying Trac first
- Once your translation is ready open a new Trac ticket, in the Localization component and attach your translation (as a .po file). You will need an account (login or register)
Guidelines on standardization in the language codes (IANA, ISO 639-2/3) and encoding (UTF-8)?
See Also
- The Kuku internationalization sample of Python i18n
- The Activities page
