Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Plant SCADA

Define an Unsupported Language

  • Last UpdatedFeb 06, 2024
  • 1 minute read

If necessary, you can define languages that are not officially supported by Plant SCADA in the Setup | Languages view in Plant SCADA Studio.

The format for specifying a non-supported language needs to follow Windows language and region definitions.

The format for specifying an unsupported language is:

<LanguageName>(<RegionName>)

For example,

"Hebrew(Israel)", where the language name is "Hebrew", and the region name is "Israel".

"Chinese (Traditional)(Taiwan)", where the language name is "Chinese (Traditional)", and the region name is "Taiwan".

When an unsupported language is specified and is used at login (that is, with the LoginForm(), Login() or UserLogin() Cicode functions), the runtime will display the prompt line "Unsupported language" and display the content in the specified language.

If the specified language is unsupported, some system texts are displayed in English rather than the specified language, such as the SOE message field. It is possible that the system may not be able to determine the character set of a non-Plant SCADA-supported language. In this case, you need to provide their desired character sets by:

  • Setting [Language]CharSet = <value>,

  • Calling ParameterPut("Language", "CharSet", <value>)

Allowable values for <value> are:

  • 0 - ANSI ASCII

  • 1 - System Default Character Set

  • 128 - Japanese - Shift JIS

  • 129 - Korean - Hangul

  • 130 - Korean - Johab

  • 134 - Chinese - simplified GB2312

  • 136 - Chinese - traditional Big5

  • 161 - Greek

  • 162 - Turkish

  • 163 - Vietnamese

  • 177 - Hebrew

  • 178 - Arabic

  • 186 - Baltic

  • 204 - Russian

  • 222 - Thai

  • 238 - East European

See Also

Set the Local Language Used at Runtime

TitleResults for “How to create a CRG?”Also Available in