* Stephen J Turnbull <stephen(a)xemacs.org> writes:
Does it really work in other ways on 21.5? I'd love to know.
Well, as long as I'm playing only with iso-8859-1, -9 and -15, the
crude patch seems to do it. At least no more multipart messages. The
real trick is that `charsets-in-region' and `charsets-in-string' seems
to do it. If I look a little bit closer, here is what I find with
21.5.9:
(loop with i = 1
while (< i 255)
collect (progn
(incf i)
(char-charset i)))
(ascii ... ascii
control-1 ... control-1
latin-iso8859-1 ... latin-iso8859-1)
All chars as expected are 8859-1 up to 255.
However this one gives only 8859-9 :
(mapcar #'char-charset '(?a ?z ?é ?è ?ç ?à ?ù ?£ ?€ ?â ?ô ?û ?î ?ä ?ü ?ë ?ï ?ö))
(ascii ascii latin-iso8859-9 ... latin-iso8859-9)
Which is confirmed by the fact that :
(mapcar #'char-int '(?a ?z ?é ?è ?ç ?à ?ù ?£ ?€ ?â ?ô ?û ?î ?ä ?ü ?ë ?ï ?ö))
(97 122 1641 1640 1639 1632 1657 1571 1700 1634 1652 1659 1646 1636 1660 1643 1647 1654)
So the chars are actually read as 8859-9. Seems wrong to me. That
should be better either 8859-1 or 8859-15. Or am I wrong ?
--
Fabrice