Activity Translations: Difference between revisions

From OLPC
Jump to navigation Jump to search
(→‎Get your strings localized: tag section as obsolete)
(Time to delete. Copies Python_i18n and locatization)
Line 1: Line 1:
{{delete}}
{{Translations}}
{{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.
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 11:11, 27 February 2008

  Trashcan.png A request has been made for this page to be deleted.
If you disagree with its deletion, please explain why on its talk page.
Before deleting verify that no links will break.
  english | português HowTo [ID# 112523]  +/-  

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
./setup.py genpot

Get your strings localized

This section is now obsolete MitchellNCharity 17:21, 29 November 2007 (EST)


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.

Click here to see all tickets for component localization and type enhancement.

See Also