
296
|
Chapter 4: Encoding Methods
Embrace Unicode and support its encoding forms, meaning UTF-8, UTF-16, and •
UTF-32. Although only one of these encoding forms typically needs to be used for
internal processing, all three must be supported in terms of interoperability.
Do not forget to support the legacy encodings—the more the better—in terms of be-•
ing able to interoperate with them.
When dealing with Unicode and legacy encodings, interoperability must be properly •
tested. Any implementation must be properly and exhaustively tested prior to its re-
lease to its users, whether they are other developers or end users.
e following sections detail these three areas of advice and provide examples of why they
are applicable to soware development.
Embrace Unicode
Embracing Unicode has its rewards, and they are great, but rewards are usually the result
of dealing with challenges. Moving from a system that uses legacy encodings to one that
uses Unicode is certainly a challenge, but the rewards are signicant. For example, GB
18030 certication, for soware developers who wish to market their products in China,
represents a signicant hurdle, but it has been demonstrated time and time again that
proper Unicode support signicantly eases the path to GB 18030 compliance.
When supporting Unicode, although it is clear that only one of its encodings needs to
be supported in terms of the processing ...