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/or "Japanese (Japan)".

   Note: You cannot refer to a regional variation of a language (for example, "French (France)") using just the neutral language name (for example, "French"). These two variations will generate and use separate databases ("French(France).dbf" and "French.dbf"). It is recommenced that you use languages that specify a regional variation.

2. In the Setup activity, select Parameters and define the default language for your project. For example, French (France).

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 DBF and insert translation (for main and include projects).

6. Recompile to include the new translations.

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

During compilation, a local language database (for example, French.dbf) is generated for each of the defined languages. 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 the defined languages would impact the project "MasterProject1" when compiled.

If your master project includes an Include project (not one of the include projects included with Plant 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 the defined languages would impact the project "MasterProject1" when linked to "IncludeProject1" which has its own existing language databases.

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 Plant SCADA Studio, Plant 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:

7. In the Setup activity, select Languages.

8. Add a row to the Grid Editor.

9. Configure the fields as required. For a description of the fields, see Languages Properties.

10. 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

Translate a Local Language Database

Officially Supported Languages

Define an Unsupported Language