We’re making changes to our server and Data Center products, including the end of sale for new server licenses on February 2, 2021 and the end of support for server on February 2, 2024. Learn what this means for you.
This guide is for translating Confluence into non-English languages using a Spreadsheet, and covers:
Improving or finishing a translation for an existing Language Plugin
Updating an existing translation for a new version of Confluence
If you do not have a Language Plugin to deploy the updated ConfluenceActionSupport_<KEY>.properties file (where <KEY> is the international language identifier), you should instead go to the Creating A New Confluence Translation.
To make small updates, it is quicker to translate the file directly. If your changes are more substantial, you may prefer to translate using Excel.
This approach uses any file editor. If your translation uses English characters, you can skip to the next section.
Preparing Non-Unicode Files For Direct Translation
If you do not have the Sun Java JDK installed, please download it now. Version 5.0 can be downloaded here.
Create a script or batch file that uses the native2ascii.exe program bundled in <JAVA-JDK-DIRECTORY>/bin to convert from the natively encoded file back to the Unicode file. For example, update the Russian properties file with a script or batch file that calls
Copy ConfluenceActionSupport<KEY>.properties to a new file ConfluenceActionSupport<KEY>-native.txt. Save the new file local non-Unicode character encoding.
Performing Direct Translation
These steps apply to both Unicode and non-Unicode translations:
Open the properties file (or it's natively encoded equivalent) for editing, translate some or all of the properties file into your target language, and save the changes. If you are translating into a non-Unicode language, always edit ConfluenceActionSupport<KEY>-native.txt, otherwise modify ConfluenceActionSupport<KEY>.properties.
Edit the file content in a text editor, referring to Translating ConfluenceActionSupport Content for more information on how to modify the string values. Users who are unsatisfied with simply opening two copies of the file in their favourite editor may want to try this freeware properties editor, that allows side-by-side comparisons.
For non-Unicode translations only, run the native2ascii script to update ConfluenceActionSupport<KEY>.properties
If you wish to test the update, copy the file back to its original location in the plugin. Then restart Confluence.
Browse to your Confluence install and go to the \confluence\WEB-INF\classes\com\atlassian\confluence\core directory. Copy the ConfluenceActionSupport.properties file there into the translation_tool directory and rename it to ConfluenceActionSupport_en.properties.
If you want to start a fresh translation, skip this step. To work from an existing translation, copy it into the translation_tool directory and remove any country variant from the filename, eg ConfluenceActionSupport_ru_RU.properties becomes ConfluenceActionSupport_ru.properties.
Call the translation tool to create the spreadsheet file. For example, to create a Russian translation, open a terminal window in the translation_tool directory and call