From: Graham Murray <newspost@gmurray.org.uk>
Subject: Re: Automatically handling different flavors of encoding?
Date: Fri, 14 Jun 2002 21:09:12 +0100 [thread overview]
Message-ID: <m3adpxk4gn.fsf@home.gmurray.org.uk> (raw)
In-Reply-To: <ugidvl6armnb7@news.supernews.com>
those who know me have no need of my name <not-a-real-address@usa.net> writes:
> but only if guessing is indicated, i.e., there is no charset specifier in
> the content-type mime header or it's a non-mime message.
MIME content-type header only applies to message/article bodies, which
in the case of the cited article only contains 7-bit ASCII
characters. The ß is in the header, so it is encoded using RFC2047,
and Kai's articles specify iso-8859-15.
next parent reply other threads:[~2002-06-14 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3k7p3a81q.fsf@kappa.unlambda.com>
[not found] ` <vaf1ybbdu5v.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <ugidvl6armnb7@news.supernews.com>
2002-06-14 20:09 ` Graham Murray [this message]
2002-06-15 9:58 ` those who know me have no need of my name
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=m3adpxk4gn.fsf@home.gmurray.org.uk \
--to=newspost@gmurray.org.uk \
/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).