*iProtect™ Translating

Owned by Tom Polman
Last updated: Sept 15, 2022
4 min read

Installation Manual | IM-20210309-TP-28

iProtect Access / Security | Installation |

This manual represents the knowledge at the above-mentioned time. TKH security works non-stop to improve her products. For the most recent technical information please contact your consultant or dealer.

1 Translating iProtect

When translating the iProtect texts, license ID-30 (translate labels) is needed.

1.1 Translating texts

Customers can adapt Dutch (language2) and German (language3) texts. The languagedependent
texts are located in the tables:

  • Column names

  • Error

  • Label text

  • Menu def

  • Subsystem

  • Table names

  • User text

The English texts cannot be modified, because they are used for re-importing the texts. If the customer chooses to modify the language-dependent texts, it is a good idea to use a separate database for this purpose (the ‘label database’).

1.2 Modifying texts

The menu texts (‘menu def’ table) and label texts (‘label text’) can be adapted by clicking on the menu item or the label by pressing the ALT button and using the right mouse button. If you click next to a label or menu, the browse form will appear. In addition to the menu items and label texts, the other texts can also be modified using this browse form. You can use the browse form to search for text fragments (start, find) or complete texts (match). The ‘&’ sign is disregarded if it is not included in the search criterion. For the label texts, an ‘&’ sign before a character means that the sign in question becomes a shortcut key. Shortcut keys are underlined. If the user presses a shortcut key in combination with the alt key, the focus shifts to the control accompanying the label and, if the control is a button, the accompanying action is performed. An ‘&’ sign is not interpreted as a shortcut key if there are two ‘&’ signs in a row. The language-dependent texts can also be exported and imported using the browse form.

1.3 Exporting texts

When exporting the texts, the user must indicate the file name and the database encoding. For most West European languages, the database encoding should be set to 0, and for several East European languages, the database encoding should be set to ISO-8859-2. If the exported file is named ‘language.xml’ and is included in the iProtect set-up instead of the original ‘language.xml’, /home/atlas/iprotect/catalina_base/webapps/Webcontrols/language) the file will automatically be imported in iProtect when iProtect is installed/started up. In this case, the iProtect version number must be different from the number stated in the ‘label text’ table (version).
When importing language-dependent texts in this way, all texts are first deleted and then the new ones are added. This method is therefore not suitable for the maintenance of the texts in the ‘label database’.

1.4 Importing texts

Connection: RS485 / 9600N81
Protocol: OSDP
Address: 0

1.5 Wiring Reader - Orion

Language-dependent texts will have been added, removed and/or modified in a newer version of iProtect. Before a new iProtect version is put on the user’s ‘label database’, the texts must first be exported (please refer to ‘Exporting texts’). Once iProtect has been upgraded, the old text file created by the user can be re-imported using the import function. Only the language dependent texts will be updated. The user has to go through the language-dependent texts once again to make sure the texts contain a correct and complete translation (the newly added labels will not have been translated).

The working method for upgrading the ‘label database’ is therefore as follows:

  1. Export language-dependent texts.

  2. Upgrade iProtect.

  3. Re-import the exported texts

  4. Recheck the language-dependent texts.

1.5 Steps

  1. Add a Translate label licence

  2. Go via ALT- and right mouse button in iProtect to the translation module

  3. Export the language.xml file

  4. Import this file in Excel (2003 or higher) with the option "use XML source pane"

  5. Make a separate tabsheet for each table, drag the XML structure of the table into it from the
    source pane and refresh the XML data (Iedata, menudef, label_text, usertext, error, Tablenames,Columnnames, subsystem)

  6. Do the translation

  7. Export (via data-xml-export) it as xml files (if it becomes too big (> 6mb) divide it via the XML nodepad).

  8. Import the files in iProtect.

2 Example

The menu texts (‘menu def’ table) and label texts (‘label text’) can be adapted by clicking on the menu item or the label using the ALT- and right mouse button.

If you click next to a label or menu item using TAB and the right mouse button, the browse form will appear. In addition to the menu items and label texts, the other texts can also be modified using this browse form. You can use the browse form to search for text fragments (start, find) or complete texts (match).

This field can also be used to import or export the language files.