From: "Bjørn Mork" <bmork@dod.no>
Cc: Simon Josefsson <jas@extundo.com>, bugs@gnus.org, bug-gnu-emacs@gnu.org
Subject: Re: bad rfc2047 encoding
Date: Thu, 22 Aug 2002 15:50:13 +0200 [thread overview]
Message-ID: <hvvg63uhnu.fsf@rasputin.ws.nextra.no> (raw)
In-Reply-To: <rzq4rdncdta.fsf@albion.dl.ac.uk> (Dave Love's message of "22 Aug 2002 12:50:41 +0100")
Dave Love <d.love@dl.ac.uk> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> Bjørn Mork <bmork@dod.no> writes:
>
> [In something that hasn't reached here...]
Sorry about that. I am also reading bugs@gnus.org via the nntp gateway
and forgot to add a Cc-header. BTW, your Cc-header did not look good:
Cc: =?iso-8859-1?q?Bj=F8rn_Mork_<bmork@dod.no>, __bugs@gnus.org,
__bug-gn?=.=?iso-8859-1?q?u-emacs@gnu.org?=
I guess this is the same problem you demonstrated in a previous
example. Never seen Gnus behave as bad as this before, though...
>> > In this example the quoted-string should probably be unquoted and
>> > then encoded. Or would that break something?
>>
>> It could perhaps encode the quotes too.
>
> The spirit of the RFC and examples seem to suggest unquoting the
> string, encoding it, and (perhaps) re-quoting encoded word sequences
> on decoding. Is the correct behaviour really not explicitly specified
> somewhere?
I am no expert on this, but trying to read RFC2822 and RFC2047 makes
me think that Simon is right. A 'quoted-string' is a 'word', and may
as such be replaced by an 'encoded-word'. The DQUOTE is part of the
'quoted-string' and should therefore be encoded with it.
So the proper way to encode
From: "Bjørn Mork" <bmork@dod.no>
would be
From: =?iso-8859-1?q?=22Bj=F8rn_Mork=22?= <bmork@dod.no>
I guess. An example of proper handling of a 'quoted-string' in RFC2047
would have been nice. But as far as I can see, this is the only way
you can do compliant encoding without losing any information.
Bjørn
next prev parent reply other threads:[~2002-08-22 13:50 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
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 [this message]
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=hvvg63uhnu.fsf@rasputin.ws.nextra.no \
--to=bmork@dod.no \
--cc=bug-gnu-emacs@gnu.org \
--cc=bugs@gnus.org \
--cc=jas@extundo.com \
/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).