On Wed, 20 Mar 2002, David Starner wrote: > On Wed, Mar 20, 2002 at 06:34:53PM -0500, Jungshik Shin wrote: > > On Wed, 20 Mar 2002, David Starner wrote: > > > > > I think what makes Ohta-san angry is that the Japanese didn't get to > > > make Unicode. When reading his complaints, I always remember that > > > they're coming from someone who put forth ISO-2022-INT, an > > > 'international' encoding that supports only Japanese and Chinese well. > > > (And maybe Korean.) > > > > ISO-2022-JP-2 tries to encode Japanese, Chinese(simplified, tranditional) > > and Korean coded character sets for mail exchange. > > ISO-2022-INT was basically an extension of ISO-2022-JP-2, with > additional Chinese charsets, keeping ASCII, ISO-8859-1 and ISO-8859-7 as > the only non-CJK charsets. It also only has KS C 5601 for Korean, so it > doesn't include a complete set of Hangul characters.
Thanks for refreshing my memory about ISO-2022-INT. I now remember it :-) BTW, even only with KS X 1001:1997(KS C 5601-1992), there IS a way to represent all modern Hangul syllables although most implementations simply chose to ignore that part in KS X 1001:1998 with Mozilla and Hanterm being notable exceptions (see http://bugzilla.mozilla.org/show_bug.cgi?id=128587 or http://jshin.net/i18n/euckr2.html) Jungshik Shin
