From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Why is UTF-8 subject base64 encoded? (ä)
Date: Thu, 18 Sep 2003 18:04:14 +0200 [thread overview]
Message-ID: <87znh2qe0x.fsf@deneb.enyo.de> (raw)
In-Reply-To: <rjwuc6tgnn.fsf@zuse.dina.kvl.dk> (Per Abrahamsen's message of "Thu, 18 Sep 2003 14:39:08 +0200")
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> The best default would probably be to try both, and use whatever is
> shortest. I believe VM does that.
Gnus does it for text/* parts, too.
next prev parent reply other threads:[~2003-09-18 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 10:37 Frank Schmitt
2003-09-18 11:11 ` Katsumi Yamaoka
2003-09-18 12:39 ` Per Abrahamsen
2003-09-18 16:04 ` Florian Weimer [this message]
2003-10-17 17:50 ` 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=87znh2qe0x.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
/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).