Providing Translations
Translations for IntelliJ Platform products and plugins can be provided in two ways:
This talk covers how to implement localization in JetBrains plugins. While JetBrains IDEs are available in Simplified Chinese, Japanese, and Korean, most plugins remain English-only. Joachim demonstrates how to easily localize different plugin elements like messages, settings, inspections, and file templates. The session also provides tips on localizing plugin descriptions for Marketplace, websites, or handbooks.
Language Packs
Localizing IDEs is achieved by providing language packs (see language packs provided by JetBrains). Language packs are IntelliJ Platform plugins containing translations of UI texts. Official language packs contain translations of all the UI texts used in the IDE and in plugins developed by JetBrains.
Note that language packs aim for full IDE localization. If it is required to translate a plugin, see the Bundled Translations section.
Language packs must define their language. The language definition is provided in the plugin.xml file with com.intellij.languageBundle extension point (EP), for example:
The locale attribute defines the translation language on two possible levels:
region level, for example:
zh-CN– Chinese (Simplified),zh-TW– Chinese (Taiwan)language level, for example,
ja– Japanese
Language Selection
In versions 2024.2 and newer language packs are bundled in IDE distributions. To select the IDE language, follow the instruction from the IntelliJ IDEA Web Help.
In versions 2024.1 and older, there is no language selector in the IDE, and language packs serve as the IDE "language switcher." Installing a language pack changes the IDE language to the one defined by the languageBundle EP. Only a single language pack can be installed at the same time, and restart is required for the translations to take effect.
Getting the Current Locale Programmatically
To get a current UI language set in the IDE, use DynamicBundle.getLocale().
Language Pack Translations Structure
See the translated elements list for the elements possible to translate. All the elements should be located in exactly the same paths as in original locations in their JAR files.
For example, if the original location of a message bundle is $PLUGIN_JAR$/messages/AbcBundle.properties, it must be located in $LANGUAGE_PACK_JAR$/messages/AbcBundle.properties.
In case of doubts, it is recommended to inspect the contents of existing language packs.
Bundled Translations
The IntelliJ Platform partially supports providing translations directly bundled in the IDE or plugins. See the translated elements list for the elements possible to translate.
An IDE module or a plugin can provide multiple language translations in a single distribution, for example, zh-CN and ja. Proper localization files will be used at runtime depending on the IDE language.
Bundled Translations Structure
Translations for a specific language can be organized in two ways as shown below. The proper directory layout/filename suffixes is the only thing needed for the translations to work. No additional actions like registering EPs are needed.
Language Directory
Translated resources are stored in a dedicated directory structure.
/localization/$LANGUAGE_CODE$/$REGION_CODE$ ($REGION_CODE$ level is optional).
Example:
Original template description:
/fileTemplates/code/JavaDoc Class.java.html
Translated template description:
/localization/zh/CN/fileTemplates/code/JavaDoc Class.java.html
Localization Suffix in Filename
Translated resources are stored in files with dedicated filename.
/intentionDescriptions/QuickEditAction/description_$LANGUAGE_CODE$_$REGION_CODE$.html
Example:
Original template description:
/intentionDescriptions/QuickEditAction/description.html
Translated template description:
/intentionDescriptions/QuickEditAction/description_zh_CN.html
Translated Elements
The following table contains the possible translated elements and information about their support in language packs and IDE/plugins.
Element | Language Pack | Bundled Translations |
|---|---|---|
(*.properties files) | Yes | Since 2024.1 Use |
(*.html files in /inspectionDescriptions directory) | Yes | Since 2024.1 |
(*.html files in /intentionDescriptions directory) | Yes | Since 2024.1 |
(*.html files in the /fileTemplates directory) | Yes | Since 2024.2 |
(*.xml file in /postfixTemplates directory) | Yes | Since 2024.2 |
Tips of the day (*.html files in tips directory) | Yes | Since 2024.2 |
See the IntelliJ Platform UI Guidelines | Text sections for good practices about writing UI texts.
Translation Lookup Order
Translations can be provided on three different levels:
region-specific translation
language-specific translation
default translation (English)
In addition, translations can be organized in directories or with file suffixes, and the same translation can be provided by a language pack or IDE/plugin.
All these conditions determine how a single translation is resolved at runtime. The lookup order is as follows:
Translation file from the language pack.
Region level (for example,
zh_CN,zh_TW) localization file:located within the localization directory of the IDE or plugin
via suffix within the IDE or plugin
Language level (for example,
zh) localization file:located within the localization directory of the IDE or plugin
via suffix within the IDE or plugin
Default file (no suffix) within the IDE or plugin (original English message).
Example
Assume that the current IDE language is set to Simplified Chinese (zh_CN). To find an example messages/MyBundle.properties message bundle for this language, the locations will be searched in the following order:
messages/MyBundle.properties (in the selected language pack plugin)
localization/zh/CN/messages/MyBundle.properties (region level)
messages/MyBundle_zh_CN.properties (region level)
localization/zh/messages/MyBundle.properties (language level)
messages/MyBundle_zh.properties (language level)
messages/MyBundle.properties (default)