Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=77325 --- shadow/77325 2006-01-27 07:44:01.000000000 -0500 +++ shadow/77325.tmp.24446 2006-01-30 02:53:49.000000000 -0500 @@ -145,6 +145,20 @@ But I have this info a different format: extracted from MultiByteToWideChar, as file windows-xp/CP28596.TXT in the tar.bz2 file found at http://www.haible.de/bruno/charsets/conversion-tables/ISO-8859-6.html, and it is the same as the ISO8859/8859-6.TXT table found on ftp.unicode.org. + +------- Additional Comments From [EMAIL PROTECTED] 2006-01-30 02:53 ------- +Oops, sorry I was too quick to think that the patch only supports your +own files. + +Hmm, WinXP mappings and Win2K mappings are the same, right? If yes, +then the latest change in I18N code would be fine. + +If no, what I still don't understand is that (according to your page) +the mapping from unicode.org the one from and Windows are "identical" +but actually the mapping from +ftp://ftp.unicode.org/Public/MAPPINGS/ISO8859/8859-6.TXT and Windows +XP mapping can differ. It is true that some of the mappings in +unicode.org are obsoleted, but (I think) it is not true to ISO-8859-6. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
