The mapping file for a new single-byte client character set, which the user creates, should contain up to four translation tables, analogous to the translation tables in DBC.CharTranslationV.
Only characters that are mapped differently from the first table should be included.
If the third table is not present, then an inverse mapping is computed from the translation defined in the first table.
The mapping file for a single-byte client character set can optionally contain the statement:
Note: If a mapping file does not specify the STATEMACHINE statement, then the default is STATEMACHINE SBC.
The STATEMACHINE statement describes the encoding form of the character set. STATEMACHINE SBC means that the character set is a single-byte character set.
The format of the mapping file is multiple lines, with each line terminated by a linefeed character. This may be problematic for editors that expect carriage-return or carriage-return followed by linefeed to terminate a line.
Note: Linefeed termination is the UNIX convention. Carriage-return linefeed is the Windows convention.
Each translation table starts with a #BEGINMAP line and ends with an #ENDMAP line. Other than those two commands, the # indicates the start of a comment that continues to the end of line. Blank lines are ignored.
The #BEGINMAP and #ENDMAP statements also include the name of the map being defined.
For an example, see “Example Mapping File” on page 91.