Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: rms@gnu.org, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Gnus does not handle quoting in quoted strings correctly.
Date: Sun, 03 Sep 2006 09:19:09 +0900	[thread overview]
Message-ID: <b4mzmdh6buq.fsf@jpl.org> (raw)
In-Reply-To: <m2mz9is6vt.fsf@kenny.sha-bang.de>

>>>>> In <m2mz9is6vt.fsf@kenny.sha-bang.de>
>>>>>	Sascha Wilde <wilde@sha-bang.de> wrote:

>> note that `\"' and `\\' in a quoted string are unchanged since
>> `"' and `\' are not qtext (cf. RFC2822 section 3.2.5).

> Sorry, I'm not sure if I understand you right.

I'm not quite sure of it but FLIM's decoder (which SEMI MUAs
such as Wanderlust uses) does so, and I followed it.

> Right now gnus (from CVS emacs) does not display quoted pairs in
> quoted strings as expected.

> Pleas note that according to RfC2822 3.2.5 quoted strings are defined
> as:

> quoted-string   =       [CFWS]
>                         DQUOTE *([FWS] qcontent) [FWS] DQUOTE
>                         [CFWS]

> where qcontent is

> qcontent        =       qtext / quoted-pair

> so quoted pairs have to be handled in quoted strings and `\"' and
> `\\' are legal quoted pairs (you can quote any "text", see RfC2822
> 3.2.1 and 3.2.2) so they must be displayed as `"' and `\'.

I agree that `\\' in a quoted string is decoded into `\'.
However, I don't think it is useful that

"foo \"bar\""  is decoded into  "foo "bar""  or  foo "bar"

because it may appear in the From header and may be used in the
To header when replying.

WDYT?

  reply	other threads:[~2006-09-03  0:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 20:38 Sascha Wilde
2006-09-01 11:09 ` Katsumi Yamaoka
2006-09-01 21:50   ` Richard Stallman
2006-09-01 22:54     ` Katsumi Yamaoka
2006-09-02  0:53       ` Miles Bader
2006-09-02 18:09         ` Richard Stallman
2006-09-02 14:03   ` Sascha Wilde
2006-09-03  0:19     ` Katsumi Yamaoka [this message]
2006-09-03 16:44       ` Sascha Wilde
2006-09-04  1:41         ` Katsumi Yamaoka

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=b4mzmdh6buq.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.
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 NNTP newsgroup(s).