Activity Translations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 32: | Line 32: | ||
== [[Translators]] == |
== [[Translators]] == |
||
* Go to |
* Go to the [http://translate.fedoraproject.org/releases/olpc OLPC release set] on [http://translate.fedoraproject.org Fedora Translations] to find out which projects needs translation and to download the current translation files (or the POT). |
||
| ⚫ | |||
** [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 <tt>.po</tt> file). You will need an account ([http://dev.laptop.org/login login] or [http://dev.laptop.org/register register]) |
* 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 <tt>.po</tt> file). You will need an account ([http://dev.laptop.org/login login] or [http://dev.laptop.org/register register]) |
||
Revision as of 09:28, 8 July 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
- 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