- From: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>
- Date: Fri, 15 May 1998 16:04:15 +0900
- To: Larry Masinter <masinter@parc.xerox.com>
- Cc: erik@netscape.com, 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
There are four proposals. Any of them is fine to me. Which is the best for IETF? Do authors of RFC2278 have any comments? Chris: This character set is not permitted for use with MIME text/* media types. Makoto: 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/*. Erik: 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). Larry: In accordance with the rules on end-of-line convention and 'text/', UTF-16 is inappropriate for use with 'text' media types. Those media types which might be deployed with UTF-16 might consider registering an 'application' type as well. 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:14:17 UTC