In this section
On this page
What is a language pack?
A language pack behaves like any other Confluence app. It is a pack of texts you translated. Every translation you create ends up stored in a language pack. Said language pack is then installed in Confluence and your translations becomes active.
How translations work in Linchpin
Linchpin Translate (part of Linchpin Manager) uses translation keys to translate content. Almost each element has an own translation key, and lucky for us, Confluence offers a relatively easy way to find out what the translation keys are.
To display translation keys in Confluence, add this parameter to the URL:
To disable the translation keys again, change this parameter to
Create a language pack
Navigate to Confluence administration → Linchpin Translations → Translate language pack.
Click on the three dots button to open a context menu. Then, click on the + New project button. Give your project (language pack) a name and click on the Save button.
Click on the New key input area at the bottom of the configuration screen. Enter the translation key here. Click on the + Add key button.
Then, click on the Locales button. Click on the first field to open a list of available languages. Select the language you want to translate into, then click on the plus button .
Repeat this step if you wish to translate the field name into multiple languages.
Click on the Close button or the X button to close this window.
Now, enter the translations into the correct fields. The languages will be displayed with the help of according ISO codes. For example, English would be
de_DE and so on.
Finally, click on the Save button.
Add as many keys and translations as you wish.
At the end, click on the Install button.
Now your new language pack is installed and active.
Important notice regarding translation keys
Please do not use the same word for the translation key and the translation.
Translations won't work when the translation key uses the same word as the translation. This is especially important when translating profile field names/field labels.
Let's say you wish to translate a profile field called
Street is the field label and at the same time the translations key.
You create 6 translations:
Users who use en_US or en_GB as their language will see
Straße as the field label.
This happens because Linchpin Translations ignores any translation that exactly matches the translation key and takes the next best translation. In this case
Straße was the first available translation that did not exactly match the translation key.