From: Dave Love <d.love@dl.ac.uk>
Cc: bugs@gnus.org, bug-gnu-emacs@gnu.org
Subject: Re: bad rfc2047 encoding
Date: 21 Aug 2002 17:54:50 +0100 [thread overview]
Message-ID: <rzqelcsdued.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: iluhehptpg8.fsf@latte.josefsson.org
Simon Josefsson <jas@extundo.com> writes:
> > Does that mean that Gnus 5.9 isn't being maintained?
>
> That wasn't what I meant. I don't know the answer.
Well, it looks that way.
> Is that necessery?
I don't know for sure, which is why I wanted someone to address it
who's more familiar with the standards than I am.
> Encoded words are allowed inside comments,
Sure.
> they must simply not contain the character ). Which the patch fixes.
It didn't seem to, but I think I fell for a defvar not getting
replaced, since the horrible mess of require'ments means you can't
unload the rfc2047 feature. [rfc2047.el really shouldn't depend on
`message-posting-charset', for instance, even if people are set
against providing a general MIME library.]
In a fresh Emacs the patched version does do the trick, thanks.
However, clearly the result for the typical form of address used in
the microshaft world is bogus:
(with-temp-buffer
(insert "To: \"Großjohann, K (Kai)\" <Kai.Grossjohann@CS.Uni-Dortmund.DE>
")
(rfc2047-encode-message-header)
(buffer-string))
=> "To: \"=?iso-8859-1?q?Gro=DFjohann,_K_(Kai)\"_<Kai.Grossjohann@CS.Uni-Dort?=
=?iso-8859-1?q?mund.DE>?=
"
Sorry, I don't have time to grovel the RFCs. Is one simply not
allowed to use such addresses? If so, Gnus should warn rather than
completely mangling it.
> I agree. (I'm reading the gnus bugs list from quimby.gnus.org, which
> removes To/Cc so when I reply it only goes to the author and
> bugs@gnus.org.)
That seems unfortunate. People reporting bugs will potentially miss
discussion.
next prev parent reply other threads:[~2002-08-21 16:54 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rzqelcsdued.fsf@albion.dl.ac.uk \
--to=d.love@dl.ac.uk \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).