From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: rfc2047 changes
Date: Thu, 20 May 2004 08:57:50 +0900 [thread overview]
Message-ID: <b9ywu38c6m9.fsf@jpl.org> (raw)
In-Reply-To: <m3hductj1n.fsf@quimbies.gnus.org>
>>>>> In <m3hductj1n.fsf@quimbies.gnus.org>
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
>> That is, if I type "=?hello?=, sailor" in a Subject header, then the
>> first word should be encoded. It's rather unlikely, but the change
>> made it necessary to delve into the bowels of rfc2047.el and hack
>> away a bit. If I broke something, give a holler...
> Found one bug. Sending via the Agent encoded things twice.
> Hm. Fixed that, but I'm starting to thing that this might not have
> been a good idea. :-)
Phew, I've merged that change into my version of rfc2047.el. :)
ftp://ftp.jpl.org/pub/tmp/rfc2047.el.gz
I will install it in Gnus CVS by the end of today (in Japan).
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2004-05-19 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 17:28 Lars Magne Ingebrigtsen
2004-05-19 17:37 ` Lars Magne Ingebrigtsen
2004-05-19 23:57 ` Katsumi Yamaoka [this message]
2004-05-20 0:39 ` Lars Magne Ingebrigtsen
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=b9ywu38c6m9.fsf@jpl.org \
--to=yamaoka@jpl.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).