From: Simon Josefsson <jas@extundo.com>
Cc: bugs@gnus.org, bug-gnu-emacs@gnu.org
Subject: Re: bad rfc2047 encoding
Date: Thu, 22 Aug 2002 19:48:52 +0200 [thread overview]
Message-ID: <ilur8gqpywr.fsf@latte.josefsson.org> (raw)
In-Reply-To: <rzqadnfcdzc.fsf@albion.dl.ac.uk> (Dave Love's message of "22 Aug 2002 12:47:03 +0100")
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?
next prev parent reply other threads:[~2002-08-22 17:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 22:00 bad rfc2047 encoding Dave Love
[not found] ` <ilu8z36li3m.fsf@latte.josefsson.org>
2002-08-20 17:02 ` Dave Love
2002-08-20 17:22 ` Simon Josefsson
2002-08-21 16:54 ` Dave Love
2002-08-21 17:06 ` Simon Josefsson
2002-08-21 17:40 ` Reiner Steib
2002-08-22 11:47 ` Dave Love
2002-08-22 17:48 ` Simon Josefsson [this message]
2002-08-30 18:08 ` Dave Love
[not found] ` <hvofbxtmpd.fsf@rasputin.ws.nextra.no>
2002-08-21 17:14 ` Simon Josefsson
2002-08-22 12:20 ` Dave Love
[not found] ` <rzq4rdncdta.fsf@albion.dl.ac.uk>
2002-08-22 13:50 ` Bjørn Mork
2002-08-30 17:59 ` Dave Love
2002-08-22 17:55 ` Simon Josefsson
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=ilur8gqpywr.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=bugs@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.