Activity Translations: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
{{Translations}}
[[Activity Translations|english]] | [Tradução de Atividades|português]]
[[Activity Translations|english]] | [Tradução de Atividades|português]]
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.
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.

Revision as of 18:16, 5 July 2007

  english | português HowTo [ID# 47893]  +/-  

english | [Tradução de Atividades|português]] 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

Guidelines on standardization in the language codes (IANA, ISO 639-2/3) and encoding (UTF-8)?

See Also