ENC API

Introduction

ENC API provides character code conversion features.

Supported Character Encodings

The internal character encoding of Revolution is UTF-16BE.

ENC API supports bi-directional conversion between the following encodings and the internal character encoding:

• US-ASCII
• UTF-8
• UTF-16BE
• UTF-32BE
• ISO-8859-1
• ISO-8859-2
• ISO-8859-3
• ISO-8859-7
• ISO-8859-10
• ISO-8859-15
• ISO-2022-JP
• Shift_JIS
• UHC
• GB2312
• windows-1252

ENC API supports a one-way conversion from the following encodings to the internal character encoding:

• UTF-7
• UTF-16
• UTF-16LE
• windows-1250
• windows-1253
• macintosh
• x-mac-ce
• x-mac-greek
• IBM850
• IBM852

Character Encoding Name Matching

ENC API matches the character encoding names based on the following rules:

1. Convert all alphabets to lower-case.
2. If the name starts in "x-" or "cs," remove them.
3. Remove all non-alphabet and non-numeric characters.
4. Compare with the matching strings of individual character encoding names.

The individual character encoding names and the matching strings are as follows:

Conversion Rules of Individual Encodings

ISO-8859

ISO-8859 conversion involves conversion from ISO-8859 to the internal character encoding and its reverse conversion.
However, in ISO-8859-1 conversion, the encoding will be treated as windows-1252 for conversion to the internal encoding, but treated as ISO-8859-1 for conversion from internal encoding.

Japanese Character Encoding

The ISO-2022-JP and Shift_JIS conversion rules will be compatible with Windows conversion with certain exceptions.

When converting from the internal character encoding to ISO-2022-JP or Shift_JIS, the following conversions not in Windows will be used.

ISO-2022-JP supports the following character groups.

• ASCII
• JIS romaji
• JIS X 0208-1983
• Half-width kana

However, JIS romaji supports only one-way conversion from ISO-2022-JP, and is treated the same as ASCII.
Half-width kana also only supports one-way conversion from ISO-2022-JP, and is converted to full-width kana at conversion to ISO-2022-JP.

For internal character encoding, the private area (1880 characters) for ISO-2022-JP and Shift_JIS are defined in the ranges shown below, corresponding to the code order.
Conversion from ISO-2022-JP is possible in the private area, but conversion to ISO-2022-JP returns ENC_ERR_NO_MAP_RULE.

Korean Character Encoding

UHC (CP949) is supported for the encoding of Korean characters.
Be aware that the size of the conversion table is larger than that for Japanese or Chinese.
The conversion target to be supported can be restricted to either of the following using the conversion table strip described below.
In either case, the size of the converted table is about the same for Japanese and Chinese.

• KS X 1001:1992 only
• Range of codes over which Chinese characters are eliminated from UHC

In the case of the former, the KS X 1001:1992 character code set is the conversion target. Hangul consists of 2350 characters.
In the case of the latter, all Hangul can be supported rather than excluding Chinese characters as conversion targets.

Conversion of the private area is not supported in both directions.

Chinese Character Encoding

With Chinese character encoding, conversion of characters not found in GB2312-80 is performed according to the internal fonts of the console.
For a listing, click here.

Conversion of the private area is not supported in both directions.

Stripping the Conversion Table

If it is not necessary to use some of the relatively large conversion tables, it is possible to strip the conversion tables by defining a macro within the program.
If you try to convert between the internal character encoding and one of the character encodings whose conversion table has been stripped, ENC_ERR_NOT_LOADED will be returned.

The currently supported macros are shown below.

See Also

List of Additional Conversion Rules for Chinese Character Encoding

Revision History

2008/02/21 Added character codes for Korean and Chinese.
2007/02/05 Added a description about stripping conversion tables.
2006/11/14 Revised description of the private area.
2006/10/24 Initial version.

CONFIDENTIAL