[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bad rfc2047 encoding
From: |
Simon Josefsson |
Subject: |
Re: bad rfc2047 encoding |
Date: |
Thu, 22 Aug 2002 19:48:52 +0200 |
User-agent: |
Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.3.50 (i686-pc-linux-gnu) |
Dave Love <d.love@dl.ac.uk> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> "To: \"=?iso-8859-1?q?Gro=DFjohann?=, K (Kai)\"
>> <Kai.Grossjohann@CS.Uni-Dortmund.DE>
>> "
>
> Well, that's invalid too.
Ouch, bad.
>> This is with EMACS_21_1_RC.
>
> I was using your patch (in a non-vanilla 21.2). It looks as though
> some of the insufficiently-tested changes I made for Emacs 22 were
> responsible for the differences, sorry. I think that just indicates
> in another way that rfc2047.el doesn't DTRT. I guess the use of Emacs
> charsets saves it from going badly wrong in this case by chance, but
> it's not generally right. It's coding systems which are
> (more-or-less) equivalent to MIME charsets and need to be checked, not
> Emacs charsets.
Yes. It would be nice to have it do the right thing, but it seem to
require at least a fairly working rfc 2822 parser/decoder. Lots of
work, I think. Anyone want to work on it?
- bad rfc2047 encoding, Dave Love, 2002/08/15
- Message not available
- Re: bad rfc2047 encoding, Dave Love, 2002/08/20
- Re: bad rfc2047 encoding, Simon Josefsson, 2002/08/20
- Re: bad rfc2047 encoding, Dave Love, 2002/08/21
- Re: bad rfc2047 encoding, Simon Josefsson, 2002/08/21
- Re: bad rfc2047 encoding, Reiner Steib, 2002/08/21
- Re: bad rfc2047 encoding, Dave Love, 2002/08/22
- Re: bad rfc2047 encoding,
Simon Josefsson <=
- Re: bad rfc2047 encoding, Dave Love, 2002/08/30
- Message not available
- Re: bad rfc2047 encoding, Simon Josefsson, 2002/08/21
- Re: bad rfc2047 encoding, Dave Love, 2002/08/22
- Message not available
- Re: bad rfc2047 encoding, Bjørn Mork, 2002/08/22
- Re: bad rfc2047 encoding, Dave Love, 2002/08/30
- Message not available
- Re: bad rfc2047 encoding, Simon Josefsson, 2002/08/22