Using Unicode Text

PML Customisation User Guide

Developing PML Code : Using Unicode Text

The AVEVA E3D™ command processor supports Unicode characters. All PML string variables support Unicode values. You can use Unicode characters in PML variable names, PML object form and gadget names, PML method and function names.

Filenames and directory names can also contain foreign Unicode characters, but remember that you may have problems saving files with foreign Unicode names in some source management systems e.g. ClearCase, so be very wary about using this facility.

At PDMS12.1 it is mandatory that PML Appware source files are stored (in order of preference) as:

Unicode UTF8 encoding with a BOM present.

Unicode UTF16 or UTF32 encoding (big-endian or little-endian) with a BOM present.

ASCII 7bit encoding – no BOM needed

Notes:

•

Using Unicode encodings with a BOM means that your (multilingual) Appware can be read successfully anywhere.

•

Restricting characters to ASCII 7bit (32 – 127) means that your (restricted) Appware can be read successfully anywhere (this is a strict subset of Unicode).

•

If you use 8-bit single byte non-Unicode characters e.g. degree sign ° (Latin1 encoding), Euro € (CP1252(ANSI) encoding), Œ (CP1252(ANSI) encoding) etc. then you will probably experience difficulty when trying to read your Appware with CADC_LANG set to Korean, Chinese, Japanese etc.