From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: improving rfc2047 encoder
Date: Mon, 17 May 2004 02:35:51 +0200 [thread overview]
Message-ID: <m3y8nryjo8.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <b9y3c5zq4ca.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> 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...
> I wish I could install it in Gnus CVS within a couple of days.
Cool.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2004-05-17 0:35 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 [this message]
2004-05-20 11:15 ` 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=m3y8nryjo8.fsf@quimbies.gnus.org \
--to=larsi@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).