Activity Translations
Revision as of 11:25, 27 July 2007 by 132.204.179.129 (talk) (→Generate the POT file for translators)
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
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 ./setup.py genpot
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
See Sugar i18n for the instructions on how to hook into the process.
See Also
- The Kuku internationalization sample of Python i18n
- The Activities page