Importing a language file
This feature enables you to import a language file into the application for a language that has already been added to the system. For existing languages, the upgrade already takes care of importing new translations that are introduced by a new software version. You do not need to import language files manually after the upgrade to update the translations. The upgrade only updates those languages for which the language files are by default delivered by Planon.
Translation keys are only imported if they are in the Planon translated (1) status. If the same translation key exists in both the application and the language file and both are in the Planon translated status, the text in the application is overwritten by that in the language file during the import. This allows translations in language files to update those in the application.
 | It is not necessary to import a complete language file. As long as the language file header is intact, you can also import a mini language file comprising of only the translation keys you want to add to or overwrite in the application. Importing fewer translation keys speeds up the import process. |
User settings
In the User groups TSI you can specify whether a user is a Translator*. The following table explains how this setting affects the application’s import process.
Import | User is a Translator | |
|---|---|---|
Transkey status in language file | Transkey status in application before import | Import result in application |
0 | (0/1/2) | Transkey is not imported and the original text remains unchanged in the application |
1 | 0 | Transkey is imported and its status changes to 1 (Planon translated). Imported text overwrites that in the application. |
1 | Transkey is imported and its status remains the same. Imported text overwrites that in the application. | |
2 | Since the user is a translator, the transkey is imported and the user translated status (2) changes to Planon translated (1). The imported text overwrites that in the application. This is because modifications made by a translator take precedence over user defined terminology. | |
2 | (0/1/2) | Transkey is not imported and the original transkey text remains unchanged in the application. A warning is added in the log viewer stating that the transkey has not been imported as it is in the wrong status. |
Import | User is NOT a Translator | |
|---|---|---|
Transkey status in language file | Transkey status in application before import | Import result in application |
0 | (0/1/2) | Transkey is not imported and the original text remains unchanged in the application. |
1 | 0 | Transkey is imported and its status changes to 1 (Planon translated). Imported text overwrites that in the application |
1 | Transkey is imported and its status remains the same. Imported text overwrites that in the application | |
2 | Transkey is not imported and the original text remains unchanged in the application | |
2 | 0 | Transkey is imported and its status changes to 2 (User Translated). Imported text overwrites that in the application |
1 | Transkey is imported and its status changes to 2 (User Translated). Imported text overwrites that in the application | |
2 | Transkey is not imported and the original text remains unchanged in the application | |
Procedure
1. In the Languages TSI, in the element section, select the language for which you want to import a language file.
2. On the action panel, click Import language.
The Upload file dialog box is displayed.
3. Click Choose file and browse to select and open the required language file.
| | The language file is only valid if the header information matches that of the selected language. If it does not match, you cannot import the language file. An error is thrown if you try to import a file with an encoding other than UTF-8. |
| | Information on the import, including import errors, is logged in Log viewer. |
4. Click OK.
The translation keys are imported into the application. A message is displayed once the import is complete. Details of the import are saved in Log viewer.
5. Click Close to complete the process.
6. Log out and log into the application again to make the changes visible.
| | If you import a language file that does not correspond with the application (i.e. if the language file version does not match that of application), modifications and new features in the application will: • Not have a translation in the relevant language • Instead have a Planon-internal translation until the correct language file is imported. For details on import errors, see Troubleshooting. |