Code-page conversion table
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Code-page conversion table
The following figure shows the format of the code-page conversion table.
|
The CONVERT keyword signals the beginning of
a code-page conversion table entry. The NOINVERSE option
of CONVERT tells OpenEdge not to create the table for
the inverse conversion. If NOINVERSE does not appear,
OpenEdge automatically creates the table for the inverse conversion. NOINVERSE is
useful for one-way conversions such as character sets for terminals
and printers. The SOURCE-NAME keyword precedes
the name of the source code page. The TARGET-NAME keyword
specifies the name of the target code page. The TYPE statement
specifies a conversion algorithm. For a conversion between two single-byte
code pages, set TYPE to 1.
To build a table to convert between two single-byte code pages, provide 256 values in 16 rows of 16 values. Be sure to format the rows of data exactly as shown in the figure.
The ENDTABLE keyword signals the end of the code-page
conversion table. The ENDCONVERT keyword signals
the end of the table entry.
To convert a character from one code page to another, OpenEdge looks in the code-page conversion table for the cell corresponding to the character's numeric value in the source code page. The cell contains the numeric value of the character in the target code page.
For example, consider converting the character "ä" from ISO8859-1 to IBM850. In ISO8859-1, "ä" has the value 228. The following example shows part of the ISO 8859-1 to IBM850 conversion table. To perform the conversion, OpenEdge looks in the table for cell 228 and finds the value 132. This value represents the numeric value of "ä" in IBM850:
|