Internationalising Confluence Plugins

Text in Confluence plugins can be internationalised to cater for a variety of locales or languages. To do this, you will need to create a translated copy of the properties file(s) for each plugin and bundle these inside your language pack plugin. Having a properties file in each plugin allows plugin authors to provide internationalised plugins without having to add their i18n keys to Confluence's core source.

Confluence comes bundled with a few plugins that are stored in a file called atlassian-bundled-plugins.zip. The basic process for translating a plugin is:

1. Extract this zip to a directory
2. Extract the plugin JAR
3. Locate the properties file which contains i18n keys (examples are below)
4. Copy this file to the same location in your plugin. For example, if it is in path/to/file.properties, it needs to be in the same place in your language pack JAR with a locale extension: path/to/file_jp_JP.properties
5. Repeat this for all plugins that can be internationalised

Below are the bundled plugins that can be internationalised and the properties file you will need to translate:

Below are the system plugins (found in confluence/WEB-INF/lib/) that can be internationalised and the properties file you will need to translate: