Activity Translations: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(link to Sugar i18n for Translators)
Line 27: Line 27:


Once that's done the people who [[Translators|care about localization]] can get the <tt>.pot</tt> files to translate and can contribute them back.
Once that's done the people who [[Translators|care about localization]] can get the <tt>.pot</tt> files to translate and can contribute them back.

== [[Translators]] ==

See [[Sugar i18n]] for the instructions on how to hook into the process.


== See Also ==
== See Also ==

Revision as of 14:57, 23 July 2007

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

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.

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

See Sugar i18n for the instructions on how to hook into the process.

See Also