Adding translations¶

There are translatable strings from both JS an Python.

We use Crowdin for translations on the project. First, you have to create an account.

After that you’ll be able to reach the crowding pages for the project and interact with translations, ex: - udata crowdin page - udata-front crowdin page

Existing languages¶

The command inv i18n extract all these strings locally. Pushing the changes on any branch will automatically update translatable strings on Crowdin.

Crowdin will submit pull requests on github each time translations are updated.

When pulling new translation in .po files, you should recompile translations with inv i18nc to generate .mo files.

Proposing a new language¶

To propose a new language you need to submit a pull request:

• create a branch for the new translations (ex: add-language-fr)
• in this branch
  • add the language to the LANGUAGES setting
  • add the language to the const languages in webpack.config.js
• submit the pull request

Once it has been accepted, we will also create the new language translation in Crowdin.

Adding translations in a plugin¶

You can also add or override some translations in your plugin (or your theme). They should be located inside your module directory and follow this layout.

├── udata_plugin
│   ├── translations
│   │   ├── xx/LC_MESSAGES
│   │   │   └── udata-plugin.po
│   │   └── udata-plugin.pot

If the translations directory is present and contains some gettext-based translations(po/mo files), they will be loaded. In the case of a theme, they will override existing ones.

The dedicated cookiecutter template makes use of Babel to extract string from your template or compile them.

You can extract translations from your own templates using:

python setup.py extract_messages  # Extract messages in your pot file

Then you can either add new supported locale:

python setup.py init_catalog -l xx  # where XX is the locale you want to add. ex: fr

or update the existing ones:

python setup.py update_catalog

You can then translate the po file using the editor of your choice. You could take a look at Poedit or set up a Crowdin project if you want.

When translation is done, you can compile translations catalogs using:

python setup.py compile_catalog  # Compile .mo files for each language