Activity Translations: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
(→‎Get your strings localized: tag section as obsolete)
Line 20: Line 20:


== Get your strings localized ==
== Get your strings localized ==

:'''This section is now obsolete''' [[User:MitchellNCharity|MitchellNCharity]] 17:21, 29 November 2007 (EST)
{{cleanup}}


* Open a new [http://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Localization&component=l10n-requests bug] on the Red Hat bugzilla. You will need to include the following information (with examples):
* Open a new [http://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Localization&component=l10n-requests bug] on the Red Hat bugzilla. You will need to include the following information (with examples):

Revision as of 22:21, 29 November 2007

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

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