[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Registration of new charset "UTF-16"

To: Chris Newman <Chris.Newman@INNOSOFT.COM>,Erik van der Poel <erik@netscape.com>
Subject: RE: Registration of new charset "UTF-16"
From: Larry Masinter <masinter@parc.xerox.com>
Date: Sat, 16 May 1998 16:11:37 -0700 (PDT)
Cc: ietf-charsets@ISI.EDU, murata@fxis.fujixerox.co.jp,Tatsuo_Kobayashi@justsystem.co.jp
Importance: Normal
In-reply-to: <Pine.SOL.3.95.980514115944.28950L-100000@elwood.innosoft.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

Follow-Ups:
- RE: Registration of new charset "UTF-16"
  - From: Chris Newman <Chris.Newman@INNOSOFT.COM>

References:
- Re: Registration of new charset "UTF-16"
  - From: Chris Newman <Chris.Newman@INNOSOFT.COM>

Prev by Date: RE: Registration of new charset "UTF-16"
Next by Date: Re: Registration of new charset "UTF-16"
Prev by thread: Re: Registration of new charset "UTF-16"
Next by thread: RE: Registration of new charset "UTF-16"
Index(es):
- Date
- Thread