CJKV Information Processing, 2nd Edition

CCS Standards

|

111

For both of these areas, support is not necessary in order to achieve certication, at least

at the time of this writing. While it is necessary for the code points for these characters

to be correctly processed, such as converting to and from Unicode and GB 18030’s native

encoding, correctly rending the characters is not necessary.

Finally, if your soware has specic areas that may be lacking in terms of GB 18030 sup-

port, it is best to identify those areas in a “ReadMe” le or other documentation that is

submitted to CESI. I want to point out that CESI would rather know about decient areas

beforehand, rather than discover them through testing.

GB 18030-2000

e original version of GB 18030, designated GB 18030-2000, was published on March

17, 2000. Its title is more complex than its 2005 revision: Information Technology—Chi-

nese Ideograms Code Character Set for Information Interchange—Extension for the Basic

Set (   xìnxī jìshù xìnxī jiāohuàn

yòng hànzì biānm zìfújí jīběnjí de kuòchōng).

Table 3-39 lists the only character whose encoding was changed for the 2005 revision.

GB 18030 encoding changesTable 3-39.

Character GB 18030 Unicode (2000) Unicode (2005)



8  77 (PUA) 13

Eectively, the change is from PUA to non-PUA, which is a very good thing, and similar

treatment is expected for 24 additional characters (see Table 3-37). ...