MusicBrainz Server/Internationalization

The MusicBrainz Server code is using gettext to provide with automatic internationalization of messages and texts used in the Perl code and templates.

A .pot file is provided with all the strings used in the server. They are in English.

Getting started

If you want to help translate, go to the Transifex page and create an account. If there is already a team for your language, you can join it, if not, you can ask for the creation of a new team.

There used to be an i18n mailing list, but it is discontinued and has been replaced by new forums (using categories and tags).

Questions or problems

If you have any questions or you're having any problems, you're welcome to ask in the #metabrainz IRC channel.

If you find a bug in the server, you can enter an issue in our bug tracker.

Viewing the translations

Some of the more complete translations (generally those over 50% translated) are available on the beta server at https://beta.musicbrainz.org/. The translations do not update automatically (see development beta cycle), but the beta server uses the same database as the main server. If you want to use the beta server all of the time for your editing, click the "Use beta site" link in the footer of https://musicbrainz.org/.

Language-specific pages

This wiki is the perfect place to discuss specific languages translations issues such as glossary, or right-to-left required patches etc.

• French

• Italian

• Polish

• Spanish

• Esperanto

• Finnish

Variables

Translatable messages not only contain plain text or HTML markup, they can also contain replaceable variables. For example:

• In {entity1} has a BookBrainz page at {entity0}, which is a URL-Work relationship link phrase, there are two entity variables whose name should not be translated, since variable {entity1} will be replaced by a work title and {entity0} by a URL.
• In link phrases, variables are often used for (optional) attributes, in order to avoid inflating the number of messages. Below are examples with the “additional” attribute:
  • {additional} will be replaced by additional if the “additional” attribute is set, otherwise it will be removed from the text.
  • {additional:additionally} will be replaced by additionally if the “additional” attribute is set, otherwise it will be removed from the text.
  • {additional:an|a} will be replaced by an if the “additional” attribute is set, otherwise it will be replaced by a.
  • {additional:%|regular} will be replaced by additional if the “additional” attribute is set, otherwise it will be replaced by regular.
  • Hence, {additional} can be translated as {additional:aldona} in Esperanto.
• Note that {instrument} and {vocals} variables are replaced by the specific instrument/vocals name:
  • {instrument:%|instruments} will be replaced by piano (or its translation) if the related instrument is “piano”, otherwise it will be replaced by instruments.