© 2008-2017, SonarSource S.A, Switzerland.
Except where otherwise noted, content in this space is licensed under a
Creative Commons Attribution-NonCommercial 3.0 United States License.

SONARQUBE is a trademark of SonarSource SA.
All other trademarks and copyrights are the property of their respective owners.

This page gives guidelines to I18n for:

• Plugin developers who would like to apply the i18n mechanism in their own plugin, so that this plugin can be available in several languages
• People who would like to help the community by making the platform available in a new language

Principles

Although the basics of the i18n mechanism are the same for every part of the ecosystem, the packaging differs depending on what you are developing:

• Translations for the SonarQube Platform: making the SonarQube Platform available in a new language requires you to develop and publish a new Language Pack plugin.
  
  • By default SonarQube embeds the English Pack.
  • All other Language Pack plugins (like the French Pack plugin) are hosted in the Plugins Forge, are maintained by the community, and are available through Update Center (category "Localization").

• Translations for the SonarQube Community Plugins: open-source plugins from the SonarQube Community (hosted in the Plugins Forge) must embed only the bundles for the default locale (en). Translations will be done in the Language Pack plugins.
  
  
• Translations for other Plugins: closed-source/commercial/independent plugins must embed the bundles for the default locale and the translations for every language they want to support.

Translation Bundles

Localized messages are stored in properties files:

• These are regular properties files with key/value pairs where you put most translations
• These files must be stored in the org.sonar.l10n package (usually in the src/main/resources/org/sonar/l10n directory)
• The names of these files must follow the convention "<key of the plugin to translate>_<language>.properties", for example "technicaldebt_fr.properties" or "core_fr.properties". See sonar-packaging-maven-plugin for details on plugin key derivation.

• Messages can accept arguments. Such entries would look like:

  myplugin.foo=This is a message with 2 params: the first "{0}" and the second "{1}".
  

Naming conventions for keys

Here is what you need to know about conventions for keys:

widget.<key>.property.<property key>.name

widget.hotspot_most_violated_rules.property.defaultSeverity.name=Default severity

widget.<key>.property.<property key>.desc

widget.hotspot_most_violated_rules.property.defaultSeverity.desc=If selected, 
severity used to initialize the dropdown list of widget

widget.<key>.property.<property>.option.<option>.name

How to use localized messages?

Java API

The component org.sonar.api.i18n.I18n is available for web server extensions. Scanner extensions can not load bundles.

Writing a Language Pack

A Language Pack defines bundles for SonarQube and/or plugins.

Creating a Language Pack

The easiest way to create a new pack is to copy the French Pack and adapt it to your language.

Maintaining a Language Pack

In the pom file, set the versions of the plugins you want to translate:

<properties>
    ...
    <!-- Versions of the plugins translated by this language pack -->
    <bundle.abacus>0.1</bundle.abacus>
    <bundle.branding>0.3</bundle.branding>
    <bundle.core>3.4-RC3</bundle.core>
    <bundle.javasquid>1.1</bundle.javasquid>
    <bundle.jira>1.0</bundle.jira>
    <bundle.motionchart>1.4</bundle.motionchart>
    <bundle.squidjava>1.0</bundle.squidjava>
    <bundle.violationdensity>1.2</bundle.violationdensity>
    ...
</properties>

When it's time to update your language pack for a new version of SonarQube or a plugin, the easiest way to see what keys are missing is to run:

mvn test

If the build fails, it means that some keys are missing. Go to target/l10n to check the reports for each bundle.

Missing keys are listed under 'Missing translations are:'

Missing translations are:
code_viewer.no_info_displayed_due_to_security=Due to security settings, no information can be displayed.
comparison.version.latest=LATEST
...

Each time you add a new bundle or update an existing one, please create a JIRA ticket on the corresponding L10n component in order to track changes.

Localizing a Plugin

This section applies if you are developing a closed-source plugin, or an open-source plugin that is not part of the SonarSonarQube Community Plugins forge.

If your plugin falls in this category, it must embed its own bundles. Bundle must be defined in src/main/resources/org/sonar/l10n/<plugin key>_<language>.properties

The default bundle is mandatory, and must be English. For example the plugin with key "mysonarplugin" must define the following files in order to enable the French translation:

• org/sonar/l10n/mysonarplugin.properties
• org/sonar/l10n/mysonarplugin_fr.properties