- From: Erik van der Poel <erik@netscape.com>
- Date: Thu, 14 May 1998 10:38:24 -0700
- To: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>
- Cc: Ned Freed <Ned.Freed@INNOSOFT.COM>, Chris Newman <Chris.Newman@INNOSOFT.COM>, ietf-charsets@ISI.EDU, murata@fxis.fujixerox.co.jp, Tatsuo_Kobayashi@justsystem.co.jp
The HTTP, HTML, XML and other communities also use IANA charsets. Various people in these communities refer to media types as "MIME types". Hence, saying "This character set is not permitted for use with MIME text/* media types" could be confusing to some people. RFC 2278 says "All registered charsets MUST note whether or not they are suitable for use in MIME." So how about rewording your sentence like this: This charset is not suitable for use in MIME email. I.e. change "permitted" to "suitable" (like 2278), and add "email" (my suggestion). Erik MURATA Makoto wrote: > We propose to register UTF-16 as a charset in IANA. UTF-16 should be > sent in network byte order (big-endian). However, recipients should be > able to handle both big-endian and little-endian. > > This character set is not permitted for use with MIME text/* media types. --Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)
Received on Thursday, 14 May 1998 10:40:59 UTC