User Defined Text; Translating User Defined Text With The Translation Tool - Omron CX-Supervisor User Manual

Translating User Defined Text with the Translation Tool SECTION 15 Multilingual Fea-
Note:

15-3-2 User Defined Text

Note:
Note:
Note:
15-4

Translating User Defined Text with the Translation Tool

228
In this context, "<Default>" means the language selected as the Default startup
language during development, in the above case Español (Spanish).
In addition, the developer may call the "SetLanguage" script function (see the
CX-Supervisor Script Language Reference Manual for details), for example
behind a button to allow the user to automatically switch languages.
While the Runtime system is shipped with full translations for all system text,
any "user defined text" added by the developer must be translated and these
translations incorporated into the application. Examples of user-defined text
are:
• Button captions, like "Open Page"
• Text in Text objects, like "Value ="
• Default values of Text Points
• Chart and Graph titles
The system always loads user defined text from files with the file name exactly
the same as the language selection, and extension ".UDT". The file names for
installed languages are: English, Czech, Danish, Deutsch, Español, Finnish,
French, Italiano, Nederlands (België), Norwegian, Polish, Português, Russian,
Slovenija, Srpski and Swedish.
IUser defined text is specific to each application, and therefore is located in the
application project directory i.e. in the same folder as the <project>.SCS file.
IIn CX-Supervisor version 1.25 and earlier the user defined text was stored in
files with a .USL extension. These files are in MBCS format. For backwards
compatibility, if these files still exist they will be loaded as MBCS and converted
to Unicode temporarily for the duration of the runtime. For this conversion to
succeed, the operating system must be configured to support displaying and
converting the original language. To permanently convert a USL translation file
to a Unicode format UDT file simply open the USL file in Notepad, select Save
As and choose Encoding "Unicode" and change the extension to UDT.
If both a UDT and old style USL file are present the Runtime will load and use
translations from the newer UDT file.
At any time during development, select Translation Tool from the Tools menu.
A dialog similar to below will be shown: