Re: XEmacs 21.5, Gnus and charsets
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
>>>>> "Fabrice" == Fabrice Popineau
<Fabrice.Popineau(a)supelec.fr> writes:
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. Or
Fabrice> am I wrong ?
>> In spirit, no.
Fabrice> I understand that. But what is the point in Xemacs saying
Fabrice> that (é) \'e is latin-9 ? It was latin-1 before being
Fabrice> latin-9 ...
It's a quirk of the Mule implementation. Mule _must_ associate a
charset with every character. This makes a politically noisy subset
of Japanese happy, and in those pre-Unicode days it was a reasonable
implementation strategy.
Why Ben changed these associations for 21.5, I don't know. I suspect
that what happens is that when the various character data is read in
from etc/unicode/unicode-consortium/8859-*.TXT Mule's idea of the
internal representation of the character gets changed every time it is
mentioned and the last of those files to mention it wins.
No, Ben didn't change this. Everything worked perfect before Ben went to
his holyday. It broke afterwards (In the last few weeks mainly). See my
post starting this thread.
--
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.