Character Sets to Code Page Mapping (All)
- Last UpdatedDec 15, 2025
- 1 minute read
You can configure the XML encoding of the generated output files, to be based on the PROJ CHARSET/PROJ MBCHARSET that the PDMS project is set to. This will make the XML text recognizable in the localised VNET installation.
Where:
<?xml version="1.0" encoding="UTF-8"?>
To change the encoding there is a configuration file where the encoding is mapped to the required code page name. A file is supplied as default which has a number of the most common mappings usually required with PDMS and VNET.
The PDMS Character Set is mapped to the required XML Codepage by the defaults file VNET-CHAR-ENCODE. The file contains a list of PDMS Character Sets and the mapped Pagecode and a description of the Language. The standard file supplied with the VNET PDMS Gateway installation is located in the PDMSDFLTS directory, %PDMSUI%\DFLTS.
|
Name |
Description |
|---|---|
|
VNET-CHAR-ENCODE |
VNET Character CodePage Mapping |
In order to keep standard (AVEVA) and user configurations separate, there can be separate VNET-CHAR-ENCODE files placed in the standard PDMS defaults areas. By default any user inclusion files found in default directories will override the supplied/standard inclusions file.
User inclusion files should have the same file name, and be placed into the following places, depending on the company standards for defaults. (This is standard to all other Marine defaults file configurations.)
-
The Marine DFLTS directory holds company exclusions, which are available to all projects.
-
The ABCDFLTS directory (where ABC is the project name) holds exclusions specific to one project.
-
The Marine USER directory holds exclusions specific to a single user.