Note: To use characters for Baltic, Central European, Cyrillic, Greek, Turkish, and Asian languages, or right-to-left languages (Arabic, Hebrew, Farsi, and Urdu) the operating system needs to have the corresponding language version of Windows, or have installed system support for that language.
languageThe language of the end user. Runtime display
items such as alarm descriptions, button text, keyboard/alarm logs,
graphic text, Cicode strings and so on can be displayed in the
local language, even though they may have been configured in the
language of the developer (native language).
need to have its own language database, so that it can be displayed
in place of a specified native language at runtime. Also, it needs
to be set as the local language using the
[Language]LocalLanguage parameter. With this
parameter set before you compile,
creates/updates the relevant language database.
For example, to display text in French at runtime,
parameter to French, flag necessary native text in the project with
@(), and compile. After compiling, look in the
project directory for French.dbf, open it,
enter the necessary French translations in the Local field, and save the database. When the project is
run, marked native text will be replaced by the appropriate French
Because you can have any number of databases, you can use as many different languages as you like.
When you compile, text marked with a language
change indicator is entered in the Native
field of whatever database is set as the local language using the
Therefore, know what database is set before you compile.
Also, if you have several language databases with
the same native language, remember that newly marked text is only
appended to the current local language
database (as specified by the
[Language]LocalLanguage parameter). To add this
text to other databases with the same native language, change the
update pages, and recompile for each database. Remember that for
each database, only relevant changes made since the last compile