The class-based API of the gettext module gives you more flexibility and greater convenience than the GNU gettext API. It is the recommended way of localizing your Python applications and modules. gettext defines a ``translations'' class which implements the parsing of GNU .mo format files, and has methods for returning either standard 8-bit strings or Unicode strings. Translations instances can also install themselves in the built-in namespace as the function _().
If localedir is not given, then the default system locale directory is used.6.3 If languages is not given, then the following environment variables are searched: LANGUAGE, LC_ALL, LC_MESSAGES, and LANG. The first one returning a non-empty value is used for the languages variable. The environment variables should contain a colon separated list of languages, which will be split on the colon to produce the expected list of language code strings.
find() then expands and normalizes the languages, and then iterates through them, searching for an existing file built of these components:
The first such file name that exists is returned by find().
If no such file is found, then
None is returned.
As seen below, you usually mark the strings in your application that are candidates for translation, by wrapping them in a call to the _() function, like this:
print _('This string will be translated.')
For convenience, you want the _() function to be installed in Python's builtin namespace, so it is easily accessible in all modules of your application.