Activity Translations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(make redir) |
||
| (20 intermediate revisions by 12 users not shown) | |||
| Line 1: | Line 1: | ||
#REDIRECT [[Localization]] |
|||
These instructions applies to a python activity using the base activity classes and the bundlebuilder. |
|||
== 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 === |
|||
* 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 |
|||
=== Add your module to Fedora Translations === |
|||
* Open a new [http://dev.laptop.org/newticket Trac ticket], in the Localization component, specifying the source repository location. |
|||
== Translators == |
|||
* Refer to the [[Activities]] page to or directly to [http://translate.fedoraproject.org Fedora Translations] to find out the translation page for a certain activity. |
|||
* 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 .po file). |
|||
Latest revision as of 22:01, 5 March 2008
Redirect to: