
696
|
Chapter 12: Web and Print Publishing
RFCs that dene ISO-2022 encodingsTable 12-2.
RFC Encoding Character sets
1554 ISO-2022-JP-2 ISO-2022-JP plus JIS X 0212-1990
b
1557 ISO-2022-KR ASCII, KS X 1001:1992
Support for JIS X 0208-1990 and JIS X 0208:1997 is also implied.a.
As you’ve read in Chapter 4, ISO-2022-JP-2 also supports GB 2312-80, KS X 1001:1992, and two parts of ISO 8859, but the GB 2312-80, KS X b.
1001:1992 character sets are better handled through RFCs 1922 and 1557, respectively.
Interestingly, although Unicode has become broadly adopted in today’s OSes and appli-
cations, ISO-2022 encoding is still used for email messages to a great extent. But, the
conversion between Unicode and the appropriate ISO-2022 encoding is handled by email
clients.
Receiving Email
Receiving CJKV text is considerably easier than sending it, especially using today’s email
clients. Displaying text is obviously easier than composing it. Still to this day, whether or
not CJKV text is displayed properly in your email client depends heavily on the extent to
which your OS has the ability to display CJKV text.
Some email clients, such as those that ran on VMS systems, did not allow control charac-
ters to function—that is, if they didn’t simply strip them out! is had the eect of render-
ing CJKV text unreadable within the email client even if you were using CJKV-capable
terminal-emulation soware. ...