Re: Brian May's `Re: Bugs in PGnus' article jams Gnus

[Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>]

ZSH> Shenghuo ZHU <URL:mailto:zsh@cs.rochester.edu>
>>>>> "ZSH" == Shenghuo ZHU <zsh@cs.rochester.edu> writes:


0> In article <2npuwiwsoe.fsf@tiger.jia.vnet>, ZSH wrote:

ZSH> In XEmacs (From the header of the message, I know Brian May use
ZSH> it), the message contains `\207', which is a `control-1' characters
ZSH> and some other `latin-iso8859-1' characters, therefore Gnus used
ZSH> multiply charsets to encode it.  Actually, Gnus can handle it as
ZSH> `iso8859-1'.  So I fixed it in latest CVS.
ZSH>
ZSH> In Emacs `\207' is an `ascii' characters, so such a message will
ZSH> not happen in Emacs.

Are you saying that with your patch, Message/Gnus will send articles
labelled as 8859.1 but containing characters in the \200-\237 range
(therefore not IS-8859.1)?  Isn't this as rude as the Microsoft stuff
that labels its Windows encoding as 8859.1?

OTOH, what is the correct action to take when we see these characters?
In this case it was a result of embedding binary data (bytecode) into
a text message - AFAICT, MIME doesn't cover this; it expects you to
put it into a non-text part (application/x-emacs-trace anyone?).