From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: UTF in messages
Date: Sat, 19 Apr 2003 20:37:50 +0200 [thread overview]
Message-ID: <84n0impc3l.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <87znmnt2d7.fsf@batman.everybody.org>
mah@everybody.org (Mark A. Hershberger) writes:
> While working on the nnrss backend, I've run into a problem with
> charsets. How do I create a message so that Gnus does the right thing
> with the charset?
What is the right thing? Gnus looks at the content and chooses some
"small" charset that includes all characters you are using. If you
use just ascii, then Gnus will choose ascii as the charset.
> 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.
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
next prev parent reply other threads:[~2003-04-19 18:37 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 [this message]
2003-04-19 18:50 ` Mark A. Hershberger
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=84n0impc3l.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).