Translation
The translation extension offers the possibility to change the question titles of a workbook in the iCL Designer. This is done via a Microsoft Excel file, where you add the different languages.
1. Export XLSX based translation file
To make the translation work, you first have to open or create a workbook in the iCL Designer.
There you can use the 'Export translation file' button to download an Excel file, where you can find all nodes of the checklists and iFindings.
After successful export, you will be notified accordingly.
You find the language export file in the specified folder:
2. Add a new Language
Every checklist and iFinding is exported to a separated excel data sheet.
In the first column you see the path of the question to identify it's position in the iCL Designer.
In column B you get the default language used in the workbook. It is labeled as 'en' and has to be changed accordingly to the used language.
You add a new language in the next free column by adding the language code in the first row. (like 'de' in column C, 'fr' in column D, and so on)
You can decide, which entries you want to translate. Every untranslated field will use the standard value from column B. If the standard language field is empty, no value will be used.
Blockly scripts with text blocks are also available for translation in a separate row.
One example of a blockly-entry is found on line 74 on the following screenshot:
3. Translation caveats
When blockly scripts are linked to answer nodes (checkbox, radiobutton, dropdown, yes/no, 3-button), keep the following situation in mind:
Answers have titles and values.
Titles will appear in the checklist in iCL.Filler. They should be translated so that they are displayed to the inspector in the right language.
Values are not translatable! You can use them to check if a specific answer was given, without worrying about the language that the inspector is working with.
When you use any of the above listed option fields, you need to be careful and use the right text block with or without localization. We suggest to always use the values instead of the titles when making a comparison in a Blockly Script, because it remains functional for all languages available in the workbook.
| Do | Don't |
|---|---|
 |  |
You can download a demo workbook from here 💾 to have a better understanding about this concept.
4. Import XLSX based translation file
When you finished the translation, you save and close the excel file and switch back to the iCL Designer.
You import the Excel document via the 'Import translation file' button.
After successful import, all translated titles, descriptions and blockly-scripts are stored internal in the workbook after saving.
If an import fails, a log file with the errors that occurred is generated and created in the export Excel folder.
5. Changes after the translation
If you modify the workbook after importing the translation, you have to keep the following behaviors in mind:
The translation of a field is lost, when:
- the field name changes
- the field moves to another checklist
- the field is removed