From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Stefan Wiens <s.wi@gmx.net>
Subject: Re: Reply misinterprets Commas in encoded-words (Gnus violates RFC
Date: Fri, 18 Feb 2005 15:44:09 +0100 [thread overview]
Message-ID: <v9k6p66i86.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b9y8y5mjm51.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 18 Feb 2005 17:41:14 +0900")
On Fri, Feb 18 2005, Katsumi Yamaoka wrote:
>>>>>> In <b9yis4ql3wu.fsf@jpl.org> Katsumi Yamaoka wrote:
>
>> I agree. Today I found a better way to fix the problem without
>> modifying the rfc2047 encoder. It doesn't require to modify the
>> way to build the reply headers either. The solution is to quote
>> decoded words in the " *gnus article copy*" buffer (in which the
>> reply headers are extracted) if there are special characters.
>> The new patch for the trunk is below.
>
> Please apply the following additional patch. It is needed so as
> not to quote words in the Subject header, etc.
The patch seems to work correctly for me (cursorily tested). It
requires some manual adaption for v5-10 (one hunk fails).
Could you please apply it to both, trunk and v5-10 (if you think it is
stable enough)? Thanks.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-02-18 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 13:31 Reply misinterprets Commas in encoded-words (Gnus violates RFC 2047) Reiner Steib
2005-02-14 7:16 ` Katsumi Yamaoka
2005-02-17 12:00 ` Katsumi Yamaoka
2005-02-17 14:07 ` Reply misinterprets Commas in encoded-words (Gnus violates RFC Reiner Steib
2005-02-18 7:32 ` Katsumi Yamaoka
2005-02-18 8:41 ` Katsumi Yamaoka
2005-02-18 14:44 ` Reiner Steib [this message]
2005-02-19 1:25 ` 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=v9k6p66i86.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=s.wi@gmx.net \
/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).