============

Translations

============

Translations are available on Hosted Weblate at the following URL:

    https://hosted.weblate.org/projects/kallithea/kallithea/

Registered users may contribute to the existing languages, or request a new

Translating using Weblate

-------------------------

Weblate_ offers a simple and easy to use interface featuring glossary, machine

translation, suggestions based on similar translations in other projects,

automatic checks etc. Weblate imports the source code tree directly from

the version control system, and commits edits back from time to time.

When registering at Weblate, make sure you use the name and email address you

prefer to be used when your changes are committed. We can and probably will

by a web hook from Our Own Kallithea every time it receives new commits. Usually merging

the new translations is a straightforward process consisting of a pull from the Weblate-hosted

repository which is available under the Data Exports tab in the Weblate interface.

Weblate tries to minimise the number of commits, but that doesn't always work, especially

when two translators work with different languages at more or less the same time.

It makes sense sometimes to re-order or fold commits by the same author when they touch

just the same language translation. That, however, may confuse Weblate sometimes, in

which case it should be manually convinced it has to discard the commits it created by

using its administrative interface.

When the Kallithea source code changes, both the location as the content of

translation strings can change. It is therefore necessary to regularly

regenerate the `kallithea.pot` file containing these strings, as well as aligning

the translation files (`*.po`).

First update the translation strings::

    python2 setup.py extract_messages

Then regenerate the translation files. This could either be done with `python2

setup.py update_catalog` or with `msgmerge` from the `gettext` package. As