UTF in messages

UTF in messages

[Mark A. Hershberger]

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?

Should I just have "Content-Type: text/html; charset='utf-8'"?  Would
that do it?  It doesn't seem to...

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

Re: UTF in messages

[Kai Großjohann]

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)

Re: UTF in messages

[Mark A. Hershberger]

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