• Intro
• Downloads
• Community
• Development
• News
• TALK

Internationalize a Python application

Revision as of 13:55, 20 December 2010

This page explains step by step how to add support for translations in a Python application for Maemo.

There are already some tutorials online about how to internationalize (i18n) Python applications, but I find them difficult to follow and they lack some needed code and final tricks to make everything work fine.

To support i18n we need to accomplish 5 tasks:

1. Define correctly a function '_()' that translates strings
2. Mark the strings in the code with that function
3. Generate a template for the translators
4. Add translations
5. Include the translations in the installation

The overall process

From the source code, using a command line tool, we will generate a ".pot" file. It is plain text file containing all strings that need translation in the project. This .pot file only needs to be generated/recreated when the strings change in the code (and not in every build!). There is only one .pot file per project.

Then, from the .pot files and using another command line tool, we will generate the .po files for each language. There is one .po file per language, and it is the file that the translators need to complete. Both .pot and all .po files should be committed in the repository.

But once your program is running, it doesn't use .po files directly, but a binary (compiled) version of them: the .mo files. These .mo files must be re-created on build time (when creating the package) and installed in the right location in the system. These are generated files, so don't commit them to the repository.

From the code point of view, you just need to call few functions to tell gettext where are the translation files, what language do you want to use (usually the locale of the environment), and then it will use its implementation to find the right string.

Ok, this is what we need to do. Let's code.

Configure gettext Define the '_()' function

If you don't care too much about the details, just copy this i18n.py file in your src/ directory (change the APP_NAME variable there!), and in every .py file in your module that needs to translate any string, add these lines at the top:

import i18n
_ = i18n.language.ugettext #use ugettext instead of getttext to avoid unicode errors

Done. If you are curious about what is going on there, the file has plenty of comments explaining every line.

Mark strings for i18n

This is one of the easiest parts. Browse the source code files that show something on the screen, and wrap the visible strings (window titles, dialog titles, notifications, labels, button labels and so on) with the '_()' function.

For example:

# import the _() function!
import i18n
_ = i18n.language.gettext
 
class Example (hildon.StackableWindow):
 
   def __init__ (self):
       hildon.StackableWindow.__init__ (self)
       self.set_title ( _("All music") )   <------- ADD THIS!

Generate template for the translators

Create a po folder in your project (usually at the same level as src/) and run the following command from the top directory of your project. You can do this inside or outside Scratchbox, there is no difference. Don't forget to replace PROJECTNAME with the name of your project.

xgettext --language=Python --keyword=_ --output=po/PROJECTNAME.pot `find . -name "*.py"`

It will parse files, written in Python, looking for strings marked with the keyword (function name) '_' and saving the output in a file called 'po/PROJECTNAME.pot'. The list of files is the last argument. I like to use "find", but you can manually put a list of files there.

That command will generate the .pot file. Easy, isn't it?

If you get the error "xgettext: Non-ASCII character at...", try to add the parameter "--from-code=UTF-8" to the command:

xgettext --language=Python --keyword=_ --output=po/PROJECTNAME.pot --from-code=UTF-8 `find . -name "*.py"`

How to add translations

Now you want to get a translation in an specific language. You need to generate a .po for it.

There are several ways to do it. I suggest to do it the easy way with poEdit:

With poEdit

Poedit is cross-platform gettext catalogs (.po files) editor. For more information, see its website http://www.poedit.net/. Just start it and generate a new catalog from the generated .pot file. In the option window you can select the translated language, your name, email address and so on. This is useful, so others know who created this translation. Default charset seems to be UTF-8. For German I had to change it to iso-8859-15, else the special characters would have looked wrong on my PC as well as on the N900 itself.

Now you can start to translate all the text. If you modify your application and generate a new .pot file, you can easily import it. It will use all the existing translation and add the new/modified strings. If you changed the charset before like me, you will have to select it again. Every time you save the file, poEdit will generate a .mo file. You can use it for testing the new translation.

Manual way

Go to the po/ folder and run this command (again, inside/outside scratchbox doesn't matter):

msginit --input=PROJECTNAME.pot --locale=LOCALE

For instance, if I want a .po file for the Spanish translation of my project Mussorgsky, I write:

msginit --input=mussorgsky.pot --locale=es_ES

It will generate a file "es.po" and translators can/must work on that file.

IMPORTANT: by default the generated .po file declares its charset as ASCII. This means that translations with non-ascii characters will provoke an error in the program. To solve this, set the charset to 'utf-8':

"Language-Team: Spanish\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"  <--- THIS MUST BE UTF-8

If you don't know the locale of a language, can check this list.

Include translations in your installation

Here again are several ways of doing it. I suggest to do it the automatic way as it is way easier if you have scratchbox.

Automatic way

If you already have the .tar.gz file, then you already have the structure with the files. Just unpack the .tar.gz file into a folder. If you have to pack it for the first time, MohammadAG has a good page about how to generate the needed files: User:Mohammad7410/Packaging

Now you will have to add some basic lines to the debian/rules file.Under the line with "install: build" should be many lines with "mkdir" and "cp -a". After the last one of them, add those two lines:

 #compile language files with msgfmt
 msgfmt src/opt/PROJECTNAME/i18n/de.po --output-file debian/PROJECTNAME/opt/PROJECTNAME/i18n/de/LC_MESSAGES/PROJECTNAME.mo

This will tell the autobuilder to generate the .mo files. You will need a line like that for every language! Don't forget to adapt the file paths. In the example the .mo files are in the sub folder i18n/de/LC_MESSAGES/

Python way

This part is more tricky, because it depends on your build system. I'll explain how it goes with the common python 'distutils' (what makes the usual python setup.py install command work). In distutils all the magic happens in the setup.py file.

First of all, if in the previous steps you have added the i18n.py file to your source tree, don't forget to include it in your data_files list!

Then, copy to the root folder of your project the file msgfmt.py. It is a program that translates the .po files into the binary .mo files that the application needs.

In your setup.py file you need to add all this code. It "overloads" the default 'build' and 'install' instructions to include the translations in the process. Now in 'build' time it will generate the .mo files (using the msgfmt.py we added just now), and in 'install' time it will include the '.mo' files in the data_files list. The code is copied from this a setup.py file.

from distutils.core import setup
from distutils import cmd
from distutils.command.install_data import install_data as _install_data
from distutils.command.build import build as _build
 
import msgfmt
import os

This command compiles every .po file under the po/ folder into a .mo (the .mo files will be under build/locale/)

class build_trans(cmd.Command):
    description = 'Compile .po files into .mo files'
    def initialize_options(self):
        pass
 
    def finalize_options(self):
        pass
 
    def run(self):
        po_dir = os.path.join(os.path.dirname(os.curdir), 'po')
        for path, names, filenames in os.walk(po_dir):
            for f in filenames:
                if f.endswith('.po'):
                    lang = f[:len(f) - 3]
                    src = os.path.join(path, f)
                    dest_path = os.path.join('build', 'locale', lang, 'LC_MESSAGES')
                    dest = os.path.join(dest_path, 'mussorgsky.mo')
                    if not os.path.exists(dest_path):
                        os.makedirs(dest_path)
                    if not os.path.exists(dest):
                        print 'Compiling %s' % src
                        msgfmt.make(src, dest)
                    else:
                        src_mtime = os.stat(src)[8]
                        dest_mtime = os.stat(dest)[8]
                        if src_mtime > dest_mtime:
                            print 'Compiling %s' % src
                            msgfmt.make(src, dest)

Now we append the previous command to the 'build' command.

class build(_build):
    sub_commands = _build.sub_commands + [('build_trans', None)]
    def run(self):
        _build.run(self)

Installation time: put every .mo file under build/locale in the data_files list (the list of things to be installed) and call the default 'install' operation

class install_data(_install_data):
 
    def run(self):
        for lang in os.listdir('build/locale/'):
            lang_dir = os.path.join('share', 'locale', lang, 'LC_MESSAGES')
            lang_file = os.path.join('build', 'locale', lang, 'LC_MESSAGES', 'mussorgsky.mo')
            self.data_files.append( (lang_dir, [lang_file]) )
        _install_data.run(self)

Finally, add the new commands in distutils...

cmdclass = {
    'build': build,
    'build_trans': build_trans,
    'install_data': install_data,
}

And don't forget to add this in your setup function, in the setup.py

setup(name         = 'your project',
      ...
     license      = 'GPL v2 or later',
     data_files   = DATA,
     scripts      = SCRIPTS,
     cmdclass     = cmdclass   <----- DON'T FORGET THIS
     )

Ok, now everything should be ready. If you run

python2.5 setup.py build

the terminal will print things like

compiling es.po
compiling de.po
...

Usually dpkg-buildpackage uses python2.5 setup.py build and install, so everything should work out-of-the-box with your previous package configuration.

Feel free to complete/correct this wiki page with your own experience.