Normally, translation is performed outside of the KNX Manufacturer Tool.
·After the product data has been prepared in the inline language, all translatable texts can be exported.
·The exported texts are processed by a translator
·The translation is then imported again into KNX Manufacturer Tool.
Small text corrections can be done directly in KNX Manufacturer Tool: By clicking the button right of the text, all translations of this texts are displayed and can be edited.
Creating new translations is not supported within the manufacturer tool, but has to be performed via the export/import mechanism described below.
To export translation data:
·open the product data file (mtxml) containing the element to be translated (e.g. an application program)
·select the element to be translated (all child elements will be included automatically)
·execute the Export Translation command (or click on the toolbar)
In the dialog appearing:
·select the translation file format (ETA or XLIFF)
·you may choose if the whole project or only the selected translation unit (application program, product, catalog section or catalog item) is exported
·select the source language; this will normally be the inline language of the element, but can also be any other language which is already completely translated.
·select the target language(s)
·enter the file name
If there are already some translated texts in the target language(s), these are written to the export file.
The list of target languages contains all languages for which translations already exist, then at most 10 (can be adjusted in the Options dialog) recently used languages, then the rest of available languages. The sections are separated by "-----" entries (which can unfortunately be selected, too, but of course are ignored).
To import translation data:
·execute the Import Translation command and select the ETA or XLIFF file to import
·select the languages to be imported.
Import will overwrite all translated texts in the selected languages. If the language is the inline language of the application program, product, catalog section or catalog item, also the texts present directly in the element are overwritten.
It can be selected if
·all translations are imported, but they are written to the product data files where the referred elements are located (recommended)
·only the translations referring to elements contained in the currently open product data file are imported.
·all translations are imported into the currently open product data file (not recommended)
After import, have a look at the output window (output from "KNX Manufacturer Tool"). If any of the imported texts is too long, a warning will be written there.
If you like to have a product data file containing only translations, you can use the method described in Product data files.
It is possible to use the export/import translation feature to correct errors in the source language, too, by selecting the source language in the import dialog.
The Check function can recognize missing translations and violations of the maximum text length.
If Microsoft Word 2007 or higher is installed, you may use the Spell Check check function for checking and correcting spelling errors.
For optical verification, use the Preview function.
·See Translation Commands for additional options.
·Be sure to translate not only the application program, but also the Product and the CatalogItem. Especially the latter is important because ETS4 import derives the import languages from the catalog translations.
Modern translation systems are capable of reading and writing XML-based files formats, and XLIFF is one of the most important of them.
For details on XLIFF, see http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html.
XLIFF files are restricted to one source and one target language per file.