Documentation for Confluence 2.5.4 - 2.5.8.
Documentation for [Confluence Cloud] and the latest Confluence Server is available too.

Text in Confluence plugins can be internationalised to cater for a variety of locales or languages. To do this, you will need to translate the properties file(s) packaged with inside each 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 and edit the properties file with your translations (more on which files to translate below)
  4. Zip the plugin back into a JAR file
  5. Repeat this for all plugins that can be internationalised
  6. Once you're done with translation, zip up all JAR files back into atlassian-bundled-plugins.zip

Here are a list of bundled plugins that can be internationalised and the properties file you will need to translate:

Plugin Name

Filename

I18N Resources

Usage Statistics Plugin

usage-tracking-plugin-<version>.jar

resources/stats/usage.properties

Atlassian Plugin Repository

atlassian-plugin-repository-confluence-plugin-<version>.jar

com/atlassian/plugin/repository/i18n.properties

Clickr Theme

clickr-theme-plugin-<version>.jar

clickr.properties

Mail Page Plugin

mail-page-plugin-<version>.jar

resources/mailpage.properties

There is a request in JIRA TRANS-38 to implement IN8 support for the Clickr Theme http://jira.atlassian.com/browse/TRANS-38





Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.