Re: Registration of new charset "UTF-16"

[erik@netscape.com (Erik van der Poel)]

MURATA Makoto wrote:
> 
>         This character set is not permitted for use with MIME text/* media
>         types.  However, the MIME-like mechanism of HTTP may use this
>         character set for text/*.

This is still likely to be confusing to people that are not so familiar
with the issues. How about being a bit more explicit, with a couple of
references. For example:

This charset is not suitable for use with text/* media types in
protocols that are sensitive to the line break issues described in
section 4.1.1 of RFC 2046 (MIME). However, this charset is suitable for
use with text/* media types in other protocols. See also section 19.4.1
of RFC 2068 (HTTP).

Also, I think the charsets in the IANA registry are used in several
protocols, some of which do not require the strict MIME line break
rules. As such, the upcoming revision of RFC 2278 should probably remove
the email bias, and allow for the other protocols that are also being
used on the Internet. The email bias could be removed by including
references to the MIME and HTTP sections mentioned above.

Erik