Re: XEmacs 21.5, Gnus and charsets

Fabrice> So the chars are actually read as 8859-9. Seems wrong to Fabrice> me. That should be better either 8859-1 or 8859-15. Fabrice> Or am I wrong ? In spirit, no. However, with conventional Mule this is hard to deal with. What should happen is that all of these characters should map to an "iso-extended-latin" charset internally, and be translated on I/O according to the coding system. (This would be fixed "automagically" if we used a Unicode internal representation, a la UTF-2000 XEmacs.) latin-unity actually implements this (crudely) by considering all of the Latin character sets as a "union" character set (where each character has multiple internal representations). GNU Emacs 21 allows you to decide which charset at read time, but I don't think you can reverse that decision easily as you can with latin-unity.[1] It looks to me like 21.5's internal implementation differs from 21.4 enough to make latin-unity non-functional. I'll try to get to this issue soon; I know how important it is. Footnotes: [1] latin-unity provides commands for the purpose, but has a number of bugs that mean it's easier said than done in some cases. However, it does work for me in many cases -- especially in my test cases. ;-) -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py