Jungshik Shin writes: > I've just found that xc/lib/X11/lcUniConv/ksc5601.h had not been > updated to reflect the change made in the standard at the end of 1998. > Could you update it in both XF86 and libiconv? I thought you had already > done that in libiconv because two characters had been added to glibc > 2.2.x. They are: > > U+20AC at row 2, column 70 (0x2266) > U+00AE at row 2, column 71 (0x2267) > > KSX1001.TXT.gz and JOHAB.TXT.gz at http://jshin.net/faq/ have been > updated to reflect this change.
Hi Jungshik, Thanks for telling me about problems in ksc5601.h, contained in both libX11 and GNU libiconv. Can you give a little more evidence/details about the standard change that you mention? The charmaps of EUC-KR on AIX, Solaris, Java don't contain the change you mention (see http://oss.software.ibm.com/cvs/icu/charset/data/ucm/), and I can find no trace of such a change on various websites. All info about these 2 character additions appears to originate from you. Unfortunately I have learned that in this table patchwork business I have to rely on several independent sources. > Most Korean truetype fonts have these two characters added This is not enough argument for adding characters to a mapping table; by the same argument we could also fill the region 0x80..0x9F in ISO-8859-1 mapping tables. > Index: ksc5601.h > =================================================================== > RCS file: /cvs/xc/lib/X11/lcUniConv/ksc5601.h,v > retrieving revision 1.4 This patch is wrong: it modifies only one of the two conversion directions and will thus cause breakage in cut&paste. Bruno _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
