From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: Brian May's `Re: Bugs in PGnus' article jams Gnus
Date: 09 Dec 1999 11:46:52 +1100 [thread overview]
Message-ID: <t4id7shj5z7.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Shenghuo ZHU's message of "Tue, 07 Dec 1999 12:45:53 -0500"
>>>>> "ZSH" == Shenghuo ZHU <zsh@cs.rochester.edu> writes:
ZSH> In XEmacs (From the header of the message, I know Brian May use it),
ZSH> the message contains `\207', which is a `control-1' characters and
ZSH> some other `latin-iso8859-1' characters, therefore Gnus used multiply
ZSH> charsets to encode it. Actually, Gnus can handle it as `iso8859-1'. So
ZSH> I fixed it in latest CVS.
ZSH> In Emacs `\207' is an `ascii' characters, so such a message will not
ZSH> happen in Emacs.
I remain skeptical that this has fixed the problem. What happens
if I send mail, with another control character, that really is
non-ASCII?
Why does Gnus have to split the message when it sees a 'bad' character?
Why can't it encode the entire message, in the same way?
Also, another question: when I saw the my message (from the URL
previously given), Gnus used 8 bit encoding. I thought 8 bit encoding
meant no encoding at all, and was considered a bad idea for non-ASCII
characters? Where am I wrong?
--
Brian May <bmay@csse.monash.edu.au>
next prev parent reply other threads:[~1999-12-09 0:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-07 13:38 Hannu Koivisto
1999-12-07 13:52 ` Gunnar Evermann
1999-12-07 14:06 ` Stein Arild Stromme
1999-12-07 14:21 ` Hannu Koivisto
1999-12-07 15:23 ` Laura Conrad
1999-12-07 16:01 ` Per Abrahamsen
1999-12-07 16:16 ` Hrvoje Niksic
1999-12-07 17:09 ` Shenghuo ZHU
1999-12-07 17:45 ` Shenghuo ZHU
1999-12-07 18:18 ` Hannu Koivisto
1999-12-07 18:22 ` Hrvoje Niksic
1999-12-07 18:57 ` Shenghuo ZHU
1999-12-07 19:21 ` Hannu Koivisto
1999-12-07 18:35 ` Toby Speight
1999-12-07 19:02 ` Shenghuo ZHU
1999-12-07 20:01 ` Jan Vroonhof
1999-12-08 9:18 ` Hrvoje Niksic
1999-12-09 0:46 ` Brian May [this message]
1999-12-09 1:11 ` Shenghuo ZHU
1999-12-09 13:37 ` Jan Vroonhof
1999-12-09 14:14 ` Per Abrahamsen
1999-12-09 15:46 ` Jan Vroonhof
[not found] ` <rj9034mcb2.fsf@zuse.dina.kvl.d <byr9gw2k2u.fsf@bolzano.math.ethz.ch>
1999-12-09 16:08 ` Per Abrahamsen
1999-12-09 19:18 ` Jan Vroonhof
1999-12-09 22:55 ` Shenghuo ZHU
1999-12-10 6:31 ` Lloyd Zusman
1999-12-10 6:42 ` Shenghuo ZHU
[not found] ` <rj9034mcb2.fsf@zuse.dina.kvl.d <byr9gvrkh2.fsf@bolzano.math.ethz.ch>
1999-12-10 8:19 ` Hrvoje Niksic
1999-12-10 9:24 ` References (was: Re: Brian May's `Re: Bugs in PGnus' article jams Gnus) Per Abrahamsen
1999-12-10 9:59 ` Hrvoje Niksic
1999-12-10 11:52 ` Per Abrahamsen
1999-12-10 10:24 ` Brian May's `Re: Bugs in PGnus' article jams Gnus Jan Vroonhof
1999-12-10 10:58 ` Broken References (was: Brian May's `Re: Bugs in PGnus' ...) Toby Speight
[not found] ` <rj9034mcb2.fsf@zuse.dina.kvl.d <byso1b14bp.fsf@bolzano.math.ethz.ch>
1999-12-10 12:06 ` Brian May's `Re: Bugs in PGnus' article jams Gnus Per Abrahamsen
1999-12-10 14:27 ` Jan Vroonhof
1999-12-10 0:46 ` Kai Großjohann
1999-12-10 3:55 ` Aaron M. Ucko
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=t4id7shj5z7.fsf@silas-2.cc.monash.edu.au \
--to=bmay@csse.monash.edu.au \
/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).