From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: address parsing problem in latest CVS
Date: Thu, 07 Sep 2006 18:54:25 +0900 [thread overview]
Message-ID: <b4mpse8knn2.fsf@jpl.org> (raw)
In-Reply-To: <b4mslj4i8p3.fsf@jpl.org>
>>>>> In <b4mslj4i8p3.fsf@jpl.org> Katsumi Yamaoka wrote:
> I started to test it using XEmacs 21.4.19, however I couldn't
> find a way to reproduce such a funny quoting so far. Could you
> let me know exactly how the headers which concern this were in
> the message buffer?
I found it. If there are two or more addresses in a header like
the following,
To: "foo bar" <foo@bar>, "foo bar" <foo@bar>
they will be encoded into:
To: "foo bar" \<foo\@bar\>\, "foo bar" <foo@bar>
I've fixed the bug in both the v5-10 branch and the trunk.
Could you try the fixed one? You can use the `C-u C-c C-m P'
command in the message buffer to see how the quoting is done.
Thank you very much for discovering this bug.
next prev parent reply other threads:[~2006-09-07 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 3:28 Dave Goldberg
2006-09-07 4:47 ` Katsumi Yamaoka
2006-09-07 9:54 ` Katsumi Yamaoka [this message]
2006-09-07 10:08 ` Katsumi Yamaoka
2006-09-07 12:01 ` Katsumi Yamaoka
2006-09-07 13:09 ` Dave Goldberg
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=b4mpse8knn2.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@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.
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).