From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Mike Kupfer <kupfer@athyra.sfbay.sun.com>, xemacs-beta@xemacs.org
Subject: Re: [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers
Date: Mon, 20 Feb 2006 16:41:31 +0900 [thread overview]
Message-ID: <b4mirrao4t0.fsf@jpl.org> (raw)
In-Reply-To: <v9irrb9bna.fsf@marauder.physik.uni-ulm.de>
>>>>> In <v9irrb9bna.fsf@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.
next prev parent reply other threads:[~2006-02-20 7:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200601280127.k0S1RqD7007468@athyra.sfbay.sun.com>
[not found] ` <87irs44xm9.fsf@tleepslib.sk.tsukuba.ac.jp>
2006-01-29 20:05 ` Reiner Steib
2006-01-29 22:24 ` Steve Youngs
2006-01-29 22:40 ` Reiner Steib
2006-01-30 1:16 ` Stephen J. Turnbull
2006-02-17 22:13 ` Date of XEmacs' Gnus (5.10.7) package (was: [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers) Reiner Steib
2006-01-30 23:24 ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Mike Kupfer
2006-01-30 23:39 ` where does package-get-info get its info from? (was: gnus 5.10.7 not rendering Latin-1 headers) Mike Kupfer
2006-01-31 1:11 ` where does package-get-info get its info from? Steve Youngs
2006-02-18 0:34 ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Mike Kupfer
2006-02-18 14:55 ` Stephen J. Turnbull
2006-02-19 12:48 ` Reiner Steib
2006-02-19 22:11 ` Mike Kupfer
2006-02-19 23:22 ` Reiner Steib
2006-02-20 7:41 ` Katsumi Yamaoka [this message]
2006-02-20 9:40 ` Katsumi Yamaoka
2006-02-20 11:30 ` Katsumi Yamaoka
2006-02-20 19:20 ` Mike Kupfer
2006-02-21 18:29 ` Mike Kupfer
2006-02-20 8:46 ` Stephen J. Turnbull
2006-02-20 9:41 ` Reiner Steib
2006-02-20 15:52 ` Stephen J. Turnbull
2006-02-20 21:26 ` Miles Bader
2006-04-09 8:14 ` Aidan Kehoe
2006-04-11 18:35 ` Reiner Steib
2006-04-13 22:34 ` Mike Kupfer
2006-04-14 8:14 ` Stephen J. Turnbull
[not found] <17990.13620.262943.353149@parhasard.net>
2007-05-13 9:20 ` Gnus: Autoloads for parse-time.el variables (was: [PATCH] package building problems.) Reiner Steib
2007-05-13 12:45 ` Aidan Kehoe
2007-05-14 17:21 ` Mike Kupfer
[not found] <m33awph096.fsf@Overgaard.mail.dk>
[not found] ` <878x6g6yz7.fsf@uwakimon.sk.tsukuba.ac.jp>
2007-10-06 16:09 ` [Bug: 21.5-b28] XEmacs/gnus refuses to open newsgroup with identical messages Reiner Steib
2007-10-07 13:47 ` Thomas Overgaard
2007-10-09 21:13 ` gnus 5.10.8 for XEmacs (was [Bug: 21.5-b28] XEmacs/gnus refuses to open newsgroup with identical messages) Mike Kupfer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mirrao4t0.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=kupfer@athyra.sfbay.sun.com \
--cc=xemacs-beta@xemacs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).