gasrasim.blogg.se - Confluence server update

#CONFLUENCE SERVER UPDATE HOW TO#
#CONFLUENCE SERVER UPDATE UPDATE#

Edit the file content in a text editor, referring to Translating ConfluenceActionSupport Content for more information on how to modify the string values.

If you are translating into a non-Unicode language, always edit ConfluenceActionSupport-native.txt, otherwise modify ConfluenceActionSupport.properties.

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.

These steps apply to both Unicode and non-Unicode translations: Save the new file local non-Unicode character encoding.

#CONFLUENCE SERVER UPDATE UPDATE#

For example, update the Russian properties file with a script or batch file that callsġ native2ascii -encoding cp1251 JiraWebActionSupport_ru_RU-native.txt JiraWebActionSupport_ru_RU.propertiesĬopy ConfluenceActionSupport.properties to a new file ConfluenceActionSupport-native.txt. Ĭreate a script or batch file that uses the native2ascii.exe program bundled in /bin to convert from the natively encoded file back to the Unicode file. If you do not have the Sun Java JDK installed, please download it now.

Preparing Non-Unicode Files For Direct Translation If your translation uses English characters, you can skip to the next section. If your changes are more substantial, you may prefer to translate using Excel. To make small updates, it is quicker to translate the file directly. If you do not have a Language Plugin to deploy the updated ConfluenceActionSupport_.properties file (where is the international language identifier), you should instead go to the Creating A New Confluence Translation.

Updating an existing translation for a new version of Confluence.

Improving or finishing a translation for an existing Language Plugin.

This guide is for translating Confluence into non-English languages using a Spreadsheet, and covers: