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

Re: Fwd: Last Call: UTF-16, an encoding of ISO 10646 to Proposed

To: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Fwd: Last Call: UTF-16, an encoding of ISO 10646 to Proposed
From: Ned Freed <Ned.Freed@INNOSOFT.COM>
Date: Sat, 18 Dec 1999 16:21:32 -0800 (PST)
Cc: MURATA Makoto <murata.makoto@fujixerox.co.jp>,Ira Mcdonald <imcdonal@sdsp.mc.xerox.com>, ietf-charsets@iana.org,yergeau@ALIS.COM
In-reply-to: "Your message dated Sat, 18 Dec 1999 21:14:31 +0100"<4.2.0.58.19991218211355.02e22050@dokka.maxware.no>
References: <199912161737.MAA25048@appsrv2.sdsp.mc.xerox.com><199912180708.AA03689@archlute.fujixerox.co.jp>

> > > I'd be delighted to see the sense of Harald's list of
> > > disadvantages captured in the actual IANA charset registration,
> > > so that implementors are sure to see the 'BEWARE'.

> > This will start heated discussion and will cause significant delay.
> > I would like to see UTF-16 registered without further delay.

> FWIW, I agree too. Get the thing out the door. As Informational.

Ditto.

				Ned

References:
- RE: Fwd: Last Call: UTF-16, an encoding of ISO 10646 to Proposed
  - From: Ira Mcdonald <imcdonal@sdsp.mc.xerox.com>
- Re: Fwd: Last Call: UTF-16, an encoding of ISO 10646 to Proposed
  - From: MURATA Makoto <murata.makoto@fujixerox.co.jp>
- Re: Fwd: Last Call: UTF-16, an encoding of ISO 10646 to Proposed
  - From: Harald Tveit Alvestrand <Harald@Alvestrand.no>

Prev by Date: Re: Fwd: Last Call: UTF-16, an encoding of ISO 10646 to Proposed
Next by Date: Re: Registration of new charsets
Prev by thread: Re: Fwd: Last Call: UTF-16, an encoding of ISO 10646 to Proposed
Next by thread: RE: Fwd: Last Call: UTF-16, an encoding of ISO 10646 to Proposed
Index(es):
- Date
- Thread