Introduction to localizing

Build 1501 on 14/Nov/2017  This topic last edited on: 26/Oct/2016, at 16:52

Localizing binary files

All GN4 binaries and add-ins expose the localizable strings, messages and dialogs boxes.

A possible localizing tool is Lingobit (www.lingobit.com) that prove to be efficient.

This does not mean that you have to use Lingobit but simply it's the only tool we tested, so far.

If you are using a different localization tool don't take too literally the descriptions in this chapter but check your user manual to understand how to apply some of the options.

See List of binary files to be localized and Localizing binary files for further details.

Localizing menus, keyboard shortcuts, entry dialog boxes, directory styles etc.

These are stored in various *_TABITEMS.XML and *_CONFIG.XML files. The process of localizing is the same as the process of customizing. Create a folder and then copy those files without renaming them, and then translate using any XML editor. For further information, see Configuring Menus, Configuring Keyboard and Mouse Shortcuts, Configuring Toolbars, Configuring Directory Styles, Configuring Entry Dialog Boxes, Configuring Preview Panes, Configuring Main and Navigator Tabs etc. See also List of configuration files to be localized.

Localizing strings

These are stored in BaseStrings.XX.xml file. See Localizing Web interface for further details. Translate using any XML editor.

Localizing data

Some default data, such as workstates or folders may be in English language. Localize them by editing their names. See Configuring GN4 User Interface for instruction on how to edit such data.