MetaBrainz:MetaBrainz.org Website/Internationalization: Difference between revisions
(→Getting started: Drop the note about testing Weblate as it has been satisfying for some time now.) |
(Reviewed many times already) |
||
| Line 28: | Line 28: | ||
A POT file is provided with all the strings used in the server. They are in English. |
A POT file is provided with all the strings used in the server. They are in English. |
||
[[Category:Internationalization]] |
|||
Latest revision as of 18:35, 12 December 2023
This page is intended for translators of MetaBrainz Foundation website, 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.
Questions or problems
To discuss about:
- MetaBrainz.org website translation/internationalization: Use the “metabrainz-website” tag in the “Internationalization” forum category (since the website has no dedicated forum category).
- General translation/internationalization: Use the “Internationalization” forum category with the appropriate tags.
To report internationalization problems about MetaBrainz.org website:
- Search for MEB tickets in the “Website” component 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
Translations are NOT currently available at https://metabrainz.org/.
More coding work is required to make it happen; See jira:MEB-65 for follow-up.
Development
The MetaBrainz.org website 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.
