
Advice to Developers
|
297
Legacy Encodings Cannot Be Forgotten
If you embrace Unicode as you should, even very tightly, legacy encodings must still be
supported at some level, in terms of interoperability. GB 18030 certication is an area that
demonstrates the need to interoperate between Unicode and legacy encodings. While em-
bracing Unicode certainly simplies the support of GB 18030-2005, one of the GB 18030
compliance requirements is to interoperate with GB 18030 encoding. ere is no escaping
this. To not support GB 18030 encoding in the context of interoperability means that your
soware cannot achieve GB 18030 certication.
In terms of legacy encodings, you should have learned that there are two basic CJKV
encoding methods, specically ISO-2022 and EUC, and a small number of locale-specic
ones. ese legacy encoding methods, at least within a single locale, are designed to in-
teroperate with one another through the use of published and well-proven algorithms.
Legacy encodings also interoperate with Unicode, some better than others, through the
use of mapping tables. For the most part, Unicode is considered a superset of the legacy
encodings. is means that data can be converted from a legacy encoding to Unicode, but
mapping from Unicode back to a legacy encoding may not be possible for some charac-
ters, depending on the target legacy encoding.
How many legacy encodings should ...