CritiqueBrainz:Internationalization
This page is intended for translators of CritiqueBrainz, and for people interested in the state of its internationalization.
Getting started
For a general introduction about translation platform, projects, and languages, please refer to the more general page about translation.
NOTE: The translations will be saved for later on as they are not currently being used in CritiqueBrainz. A patch is on its way to restore this feature though.
Questions or problems
To discuss about:
- CritiqueBrainz translation: Use the “translation” tag in the “CritiqueBrainz” forum category.
- CritiqueBrainz internationalization: Use the “internationalization” tag in the “CritiqueBrainz” forum category.
- General translation/internationalization: Use the “Internationalization” forum category with the appropriate tags.
To report internationalization problems about Critiquebrainz:
- Search for MBS tickets with “internationalization” label and create a new ticket if not found.
For more real-time interactive conversation with developers, you’re welcome to ask in the #metabrainz IRC channel.
Viewing the translations
Some of the more complete translations are available on the only server at https://critiquebrainz.org/.
The translations do not update automatically, they are updated at release time only.
Development
The CritiqueBrainz server code is using gettext to provide with automatic translation of messages and texts used in the Python code and Jinja2 HTML templates.
A POT file is provided with all the strings used in the server. They are in English.
See developer documentation at:
- https://critiquebrainz.readthedocs.io/intro.html#modifying-strings
- https://critiquebrainz.readthedocs.io/translation.html
Beyond translation
- CritiqueBrainz supports writing reviews in an auto-detected/manually selectable language.
