Setup > Languages > Prepare a Project for Multi-language Support > Defining the languages supported by a project | Setup

Define the Languages Supported by a Project

To set up multi-language support in your project, complete the following:

  1. In the Setup activity, define the required Languages for the main project. For example, French (France) and Japanese (Japan).
  2. From the Setup activity, select Parameters and define the default language for your project. For example, French.
  3. In the include project (if any and not a standard Include project) define languages in the Setup activity. For example, French (France) and Japanese (Japan).
  4. Compile and generate the language DBFs.
  5. Open each language DBFs and insert translation (for main and include projects).
  6. Recompile to reflect new translations.

Note: The language defined in the Citect.INI file will take precedence over the default language defined in your project.

On defining your required languages in Citect SCADA this will update the project database LANG.dbf. This database is used to specify the local languages you would like a project to support. It also determines if OEM conversion is required for a particular language.

Next define the default language to be used in your project. This needs to be one of the languages you defined in the Lang.dbf.

During compilation, a local language database (eg. French.DBF) is generated for each language defined in LANG.dbf. If the project, does not have an existing database for one of the specified languages, one will be created with its native column populated with native strings and local column empty.

Once this process is complete, an .rdb file is added to the master project for each defined language to facilitate the operation of multi-language switching during runtime.

The following table provides an example of how LANG.dbf would impact the project "MasterProject1" when compiled.

Project name

Lang.DBF languages

Existing and newly defined language databases

.dbf Files created during compilation

.rdb files created during compilation

   

Local Language Databases

Runtime Database

MasterProject1

French(France)
English
Japanese(Japan)

English.dbf

French(France).dbf
Japanese(Japan).dbf

lanen.rdb
lanfr-fr.rdb
lanja-JP.rdb
Plus RDBs for languages defined in default include projects

If your master project includes an Include project (not one of the include projects included with Citect SCADA) you will need to define the supported languages within your include project as well as in the master project.

The following table provides an example of how LANG.DBF would impact the project “MasterProject1” when linked to "IncludeProject1" which has its own existing language databases.

Project name

Lang.DBF languages

Existing and newly defined language databases

.dbf Files created during compilation

.rdb files created during compilation

   

Local Language Databases

Runtime Database

MasterProject1

French(France)
English
Japanese(Japan)

English.dbf

French(France).dbf (1)
Japanese(Japan).dbf

lanen.rdb
lanfr-fr.rdb (1 & 2 are merged)
lanja-JP.rdb
lanko-KR.rdb
Plus RDBs for languages defined in default include projects

IncludeProject1

French (France) English
Korean(Korea)

 

English.dbf
French.dbf (2)
Korean(Korea).dbf

 

If a project and one of its included projects have variations of the same language database, the translations will be merged into the ‘.rdb file’, in the table above the French files (1 & 2) were merged.

You can also see that during compilation the Korean.dbf was created and added to the "MasterProject". Once you have defined the required languages, and defined the default language for your project you can open the language DBFs and insert translation (for main and include projects).

Note: If you do not define any languages in LANG.dbf, Citect SCADA will create a default file _lanEN.rdb The native text will be used for the associated translations.

To define the languages supported by a project:

  1. In the Setup activity, select Languages.
  2. Add a row to the Grid Editor.
  3. Configure the fields as required. For a description of the fields, see Language Properties.
  4. Click Save.

Note: When setting the properties for you will be required to associate a setting for the parameter [CTEDIT]ANSIToOEM for each language. This parameter defines whether or not the language requires translation to OEM. See the topic OEM character sets for more information.

See Also

Published June 2018