Translate Profile Field and Profile Section Names
How it works
To translate the names of profile fields or profile sections, we will use Linchpin Translations. Usually, Linchpin Translations uses specific keys as translation base (for example administration.global.menu.label). In case of Linchpin User Profiles, this procedure gets a little bit simpler.
The translation key is equal to the profile field/section name (also called field label).
Inside Linchpin Translations, you can then enter the translation key (= field label = field name) and add locales (= translations).
Once done, you can install this language pack to Confluence. The language pack will then automatically apply translations, whenever and wherever available.
Configure profile field/section translations
Prepare profile fields/sections
Navigate to Confluence administration → Linchpin User Profiles → Profile Editor.
Either leave this page open or note all profile field and section names you wish to translate. Remember, the value that’s translated is “field label”.
We strongly advise to avoid spaces in field labels!
Linchpin Translations can encounter some errors when spaces are used in translation keys. Since field labels are the translation keys for Linchpin User Profiles, you should try to avoid spaces in profile field names.
Create a translation 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 field label/field name 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 en_US, German 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.
If your key changes to undefined after you hit save, please enter the key (field name) again.
Sometimes this error might occur, but you will solve it when you re-enter the field name and click on the Save button again.
Now your new language pack is installed and active.
When the user uses a browser language which has not been translated, and their Confluence language is based on their browser, the user will see the default profile field names.
Example
You created a profile field name named “Country”. Inside Linchpin Translations, you translated this key into three languages: English (Country), German (Land), Polish (Kraj).
The user has a browser with Spanish as the default language. The Confluence language they use is based on their browser (Spanish, in this case). The user will see this profile field as “Country”, since Spanish was never added to the translations. Therefore, the default value is used.
Translate the help text
You can also translate the help text field. The helps text field should be used to give users advices on how to fill out a specific profile field. Users can find the help text while they edit their profile. It will be displayed as an icon (❓) next to the profile field.
To translate the help text, you need to create a translation key. It can be anything. In our example, we will call it helptext.
You can enter this key in every help text field that fits the translation. Here, we will only use the Languages field.
Then, navigate to Confluence administration → Linchpin Translations → Translate language pack.
Create a new project or open a project you used before.
Follow the instructions above, but keep in mind:
Key = the key you created and entered in every text help field.
Translation = the “true” help text in the correct language. Enter your help text here.
Since the standard value for the help text is the created key, you need to add an English translation, too!
Otherwise, users with English as their default language will only see the translation key.
Link to this page: https://seibert.biz/translateprofilefields
