From MusicBrainz Wiki
Revision as of 20:28, 20 December 2023 by YvanZo (talk | contribs) (→‎Languages: Unlisting the unreviewed/inactive language pages (Esperanto/Finnish/Polish) - Feel free to (re)list any page active (again))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

This page is about internationalization of MetaBrainz projects, which means making the projects support different languages and work as expected in different regions. The main section below is about translation of the projects’ user interface: being able to provide the software itself in different languages. The rest is about more general issues, such as correctly handling data from different languages and different regions.


This section is intended for translators of projects related to the MetaBrainz community.


We have a dedicated translation platform which you can use with your MusicBrainz account. It is hosted by the Weblate team, with a data processing agreement in conformity to the GDPR. Note that the legal terms are generic to all Weblate instances and that “purchase” isn’t available from MetaBrainz Weblate instance.

See the Weblate user docs for a general introduction on how to use the platform.


Each of the translation projects has an “Info” tab linking to one of the below wiki page that gathers project-specific information for translators and, more generally, about internationalization for that project:

Note: The following official MetaBrainz projects aren’t translatable at the moment: BookBrainz, Cover Art Archive, and ListenBrainz. The archived projects AcousticBrainz and MessyBrainz have never been (and won’t ever be) translatable.

Our platform isn’t limited to official projects maintained by the Foundation, and we also host translations for community projects. If you have a MetaBrainz-related project you want to make translatable, such as a script or extension, get in touch!


Among all the languages we currently support on Weblate a fair amount are likely to contain only old translations and not have any recent activity, and not all projects are available for all languages yet. You can find out more by clicking on the desired language; projects supporting the language will be listed on the “Projects” tab and activity data on the “Information” tab.

If a language is not available at all or your language is not available for the project you want to translate, just ask for it on the “Internationalization” community forum category.

To help with coordinating translations in the same language, you can use Weblate glossaries and comments, the MetaBrainz community forums (see below questions or problems), and/or a wiki page (create one if missing):

Beyond translation


Discourse’s user interface is localized.

  • The few topics written in a language other than English can use tags such as de for Deutsch (German). A separate selector is available and language names are localized using the Multilingual plugin.
    There is a topic about making this practice official.
  • Pinned welcome topics are not localized, the same topic as above is also about localizing welcome topics.
  • Category titles are now localized using the Multilingual plugin.
  • Some semi-static texts are not localized. It could be implemented in Multilingual Plugin if anyone feel up to coding for this Ruby project.
  • Content is not translated. The Translator plugin could be considered.
  • The ListenBrainz plugin can be translated in the project Discourse ListenBrainz on the MetaBrainz Weblate translation platform.


Jira’s user interface is localized.

Note that the content doesn’t have to be localized since English is the work language for the MetaBrainz team. (Tickets reported in another language would probably be translated in English and replied in both languages.)


MediaWiki’s user interface is localized but not the content, which is generally assumed to be in English (with a few exceptions such as language translation project pages).

We gave up using the Content translation tool due to incompatibilities at that time and inability to ensure consistency with other translations unless using Translate extension instead of Transifex or Weblate; See comments to jira:OTHER-350 for details.

Translation platform

Weblate’s user interface itself is localized.

Questions or problems

To discuss about:

To report problems:

For more real-time interactive conversation with developers, you’re welcome to ask in the #metabrainz IRC channel.