From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: improving rfc2047 encoder
Date: Thu, 20 May 2004 20:15:58 +0900 [thread overview]
Message-ID: <b9yr7tffixd.fsf@jpl.org> (raw)
In-Reply-To: <m3y8nryjo8.fsf@quimbies.gnus.org>
>>>>> In <m3y8nryjo8.fsf@quimbies.gnus.org>
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
>> This header can be encoded as follows. It still honors the
>> 76-column rule which is described in the RFC2047 section 2.
>>
>> Subject: Re: =?iso-2022-jp?B?GyRCPHc4Qkw1PHc4Qkw1OF45ZSROJDkkakBaJGwbKEI=?=
> Great! The unnecessary folding has annoyed me, too...
Thanks! I've installed the new MIME header encoder in Gnus CVS.
Although it is probably incomplete, the new encoder is much
better than the former version. If you feel uneasy, please type
the `C-u C-c C-m P' command in advance whenever you send mails.
Regards,
P.S. Encoding `=?foo' things in the address headers has not been
implemented yet.
--
Katsumi Yamaoka <yamaoka@jpl.org>
prev parent reply other threads:[~2004-05-20 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 0:34 Katsumi Yamaoka
2004-05-17 0:35 ` Lars Magne Ingebrigtsen
2004-05-20 11:15 ` Katsumi Yamaoka [this message]
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=b9yr7tffixd.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).