RE: Registration of new charset "UTF-16"

• From: Larry Masinter <masinter@parc.xerox.com>
• Date: Sat, 16 May 1998 16:11:37 -0700 (PDT)
• To: Chris Newman <Chris.Newman@INNOSOFT.COM>, Erik van der Poel <erik@netscape.com>
• Cc: ietf-charsets@ISI.EDU, murata@fxis.fujixerox.co.jp, Tatsuo_Kobayashi@justsystem.co.jp
• Message-id: <000001bd811f$fa1cc280$15d0000d@copper-208.parc.xerox.com>

> We might eventually define a MIME "widetext" top-level media type for
> plaintext data using UTF-16 or UCS-4, but I don't think it's time to do
> that yet.  UTF-8 is standards track and may be freely used in text/* media
> types.


I think it's time to do this. It's been a recurring issue for as long
as I've been trying to work the 'charset' issue in HTTP. What's needed
is something that just doesn't have the same end-of-line handling that 'text'
has, so I believe 'etext' would do.

Larry



--Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)

Received on Monday, 18 May 1998 11:07:48 UTC