Re: UTF-16 and MIME text/*

* John Cowan wrote:
>Bjoern Hoehrmann scripsit:
>
>>    RFC 2871 registers all UTF-16 charsets (UTF-16BE, UTF-16LE and
>> UTF-16) as not suitable for use in MIME content types under the
>> "text" top-level type. Why?
>
>Because a MIME processor, when encountering something of type text/*,
>is allowed to assume that any 0x0A byte means "LF" and any 0x0D byte means "CR",
>and to transmute them to some other kind of line ending.  UTF-16
>of whatever flavor violates this rule.

Could you please give me some reference where MIME allows applications
to _transmutate_ them? Someone poited out to me, that RFC 2871 is in
error here and I tried hard to find something in MIME that clearly
states, that RFC 2871 is correct in this regard.

TIA,
-- 
Björn Höhrmann { mailto:bjoern@hoehrmann.de } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

Received on Saturday, 11 August 2001 19:42:43 UTC