[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>
Subject: Re: Registration of new charset "UTF-16"
From: "Martin J. Duerst" <duerst@w3.org>
Date: Mon, 18 May 1998 13:01:12 +0900
Cc: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>, erik@netscape.com,ietf-charsets@ISI.EDU, murata@fxis.fujixerox.co.jp,Tatsuo_Kobayashi@justsystem.co.jp
In-reply-to: <Pine.SOL.3.95.980515090408.594C-100000@elwood.innosoft.com>
References: <199805150119.AA01051@murata.apsdc.ksp.fujixerox.co.jp>

At 09:04 98/05/15 -0700, Chris Newman wrote:
> On Fri, 15 May 1998, MURATA Makoto wrote:
> > 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/*.
> 
> That sounds reasonable.

Yes indeed.

Something else that should be added to the registration information
is that UTF-16 always should refer to the newest version of Unicode/
ISO 10646. This has been discussed on the unicore list, but not here,
but it is very crucial.

Regards,   Martin.

Follow-Ups:
- Re: Registration of new charset "UTF-16"
  - From: Chris Newman <Chris.Newman@INNOSOFT.COM>
- Re: Registration of new charset "UTF-16"
  - From: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>

References:
- Re: Registration of new charset "UTF-16"
  - From: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>
- Re: Registration of new charset "UTF-16"
  - From: Chris Newman <Chris.Newman@INNOSOFT.COM>

Prev by Date: Revised proposal for 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