- From: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>
- Date: Fri, 15 May 1998 10:19:45 +0900
- To: erik@netscape.com
- Cc: Chris Newman <Chris.Newman@INNOSOFT.COM>, Ned Freed <Ned.Freed@INNOSOFT.COM>, ietf-charsets@ISI.EDU, murata@fxis.fujixerox.co.jp, Tatsuo_Kobayashi@justsystem.co.jp
In message "Re: Registration of new charset "UTF-16"", Erik van der Poel wrote... > Are you saying that the MIME standard somehow attempts to specify what is or is not > allowed in other protocols, like HTTP, HTML, XML, etc? > > Or are you referring to other email-like protocols, like NNTP perhaps? Or ACAP? Or > IMAP? POP? > > Please elaborate. HTTP 1.1 uses a MIME-like mechanism. The difference between this mechanism and "100% pure MIME" is shown in an appendix of HTTP 1.1. Having said this, I understand Erik's concern. Most people think HTTP uses MIME and will be confused. I would propose to revise the sentence as below: 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/*. [Fri, 15 May 1998 10:12:50 +0900] Makoto Fuji Xerox Information Systems Tel: +81-44-812-7230 Fax: +81-44-812-7231 E-mail: murata@apsdc.ksp.fujixerox.co.jp --Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)
Received on Monday, 18 May 1998 11:13:48 UTC