Re: [VM] Incorrectly encoded non-ASCII headers

[Yeechang Lee]

Uday Reddy <address@hidden> says:
> What character set are the headers in?

From Wikipedia:
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

From The New York Times:
Content-Type: text/html; charset=utf-8; format=flowed
Mime-version: 1.0

From Open Library
Content-Disposition: inline
Content-Type: text/plain; charset=UTF-8
MIME-Version: 1.0

From Soap.com (subject incorrectly displayed in summary, but
correctly displayed in presentation buffer. Only one in which Unicode
is not involved.):
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I can send the messages as attachments off-list if helpful.

PS - On reflection, of the choices I earlier mentioned:

> could VM gain the ability to assume that the body's encoding style
> in a message also applies to the headers? An alternative would be to
> assume that headers are 8-bit clean unless RFC 2047-style quoting
> appears

I suspect that the second is preferable, as amended:

> Assume that human-readable headers are 8-bit clean and in UTF-8
> unless RFC 2047-style quoting appears

Setting aside cases in which the encoding header is incorrect, I'm
pretty sure I've seen messages in which header and body encodings
don't match.

Perhaps the above should apply to the body as well? (Or does it
already? I have one in my folder of test messages I've received over
the years in which Content-Type: only says "text/plain;", nothing
else, despite Unicode in the body. VM displays the message correctly
in Emacs 23.)

-- 
geo:37.783333,-122.416667