>>>> In <v9irrb9bna.fsf(a)marauder.physik.uni-ulm.de>
Reiner Steib wrote:
Leaving this for the XEmacs folks...
> The docstring for mm-coding-system-p says it returns "a coding system
> object in XEmacs". The XEmacs Lisp reference talks about coding
> systems, under MULE. Does that mean that coding system objects only
> exist in MULE XEmacs? What should (mm-coding-system-p 'iso-8859-1)
> return in non-MULE XEmacs?
I have five XEmacsen installed. Those are:
1. 21.4.19 with mule with file-coding
2. 21.4.19 with mule without file-coding
3. 21.4.19 without mule without file-coding
4. 21.5-b24 with mule with file-coding
5. 21.5-b24 without mule with file-coding
Only 3 doesn't have coding system functions including
`decode-coding-string', `encode-coding-region', etc., and mm-util
makes them all aliases to `identity', `ignore' or equivalents.
Even so, if I understand it correctly, that version of XEmacs
displays 8-bit data as Latin-1 characters. For example:
(insert "\310")
È
(mm-decode-coding-string "\310" 'iso-8859-1)
"È"
(mm-decode-coding-string "\310" 'any-coding-system)
"È"
The last example suggests we can make `mm-coding-system-p' return
any value, that is, it doesn't have to be a coding system object.
Actually, the following form works:
(let ((mm-coding-system-list '(iso-8859-1)))
(rfc2047-decode-string
"=?ISO-8859-1?Q?Ignacio_Marambio_Cat=E1n?="))
"Ignacio Marambio Catán"
So, changing
(defvar mm-coding-system-list nil)
to
(defvar mm-coding-system-list '(iso-8859-1))
in mm-util.el will solve at least the problem that Mike Kupfer
first brought up. Is there any coding systems which should be
added to the default value other than iso-8859-1 that XEmacs
without mule without file-coding supports?
I'm not sure it solves all problems with Gnus and that version
of XEmacs, though.