Troubleshooting - Language file import
 | Always check the import log in System info > Log viewer for details on import errors and warnings. |
Error | Cause |
|---|---|
Critical error: import stops | The language file and selected language are not the same |
Outcome and remedy | The Code and the Locale (regional settings) in the header of the language file must match the selected language. Use the correct language file |
Critical error: import stops | A header field is empty. |
Outcome and remedy | The language file’s header information must be complete. The following header parameters must always have a value specified: Language Code Default Description Planon release and build Use the correct language file. The remaining header fields can either have a value specified or a hash mark (#) as a placeholder. |
Warning; import will continue | The version of the language file does not match the application version |
Outcome and remedy | The language file will not contain all translations. The missing items will be assigned the default translation in the application. The language file contains translations that are no longer applicable. These translations will not be imported. Use the latest language, or export a new language file, edit the relevant translation strings and then re-import the language file. |
Warning; import will continue | Duplicate keys in language file |
Outcome and remedy | The language file contains the same translation key twice. As there can only be one translation key, the second key is skipped during import. In the import language file, locate and delete the duplicate key(s) and re-import the language file. |
Warning; import will continue | The language file contains a translation key that is not in the application. |
Outcome and remedy | The version of the language file does not match that of the application. The translation key is skipped during import. Import the latest language file. |
Warning; import will continue | The text in a translation key exceeds the 500 character length restriction |
Outcome and remedy | The key that is too long is skipped during import. Edit the translation key text so that it is within the 500 character limit. |
Warning; import will continue | Incorrect translation key syntax |
Outcome and remedy | The syntax of a translation key (see translation key example for correct syntax). The translation key containing the incorrect syntax is skipped during import. Use the correct syntax. |
Warning; import will continue | Translation key is in the “not translated” (0) status. |
Outcome and remedy | The translation key is not imported. Translate the text of this transkey and then change its status to “Planon translated” (1). |
Newly imported translations do not appear on screen | A new language file is imported containing changes to translation keys. However, the changes do not appear on the screen. |
Outcome and remedy | There may be various solutions to this problem. • Ensure that you are identified as a Translator (go to Accounts > User groups > Settings). As this setting affects the import process, carefully read the documentation and familiarize yourself with the implications of using this setting. • Ensure your user settings reflect the language you have just imported. If another language is selected, the changes will not be visible. Restart the application to make the changes effective. • Purge your browser's history and cache and log in again. |