From: mah@everybody.org (Mark A. Hershberger)
Subject: Re: UTF in messages
Date: Sat, 19 Apr 2003 13:50:59 -0500 [thread overview]
Message-ID: <87ademnwx8.fsf@batman.everybody.org> (raw)
In-Reply-To: <84n0impc3l.fsf@lucy.is.informatik.uni-duisburg.de>
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> mah@everybody.org (Mark A. Hershberger) writes:
>> Should I just have "Content-Type: text/html; charset='utf-8'"? Would
>> that do it? It doesn't seem to...
>
> ?? text/html? Hm.
>
> I don't think manually adding a Content-Type header will do anything,
> except perhaps annoy Gnus.
In this case, the "text/html" is there because that is what the
content is (and people who have mm-text-html-renderer set up will get
some benefit). The "charset=..." part is what I was looking at.
Mark.
--
You are a mystery as deep as the sea; the more I search, the more
I find, and the more I find the more I search for you.
-- St. Catherine of Siena
prev parent reply other threads:[~2003-04-19 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 6:42 Mark A. Hershberger
2003-04-19 18:37 ` Kai Großjohann
2003-04-19 18:50 ` Mark A. Hershberger [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=87ademnwx8.fsf@batman.everybody.org \
--to=mah@everybody.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).