Re: 10646 & Unicode
Keld Jørn Simonsen <[email protected]> Tue, 6 Jan 2004 11:07:43 +0100
| Newsgroups | gmane.ietf.imaa |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jan 05, 2004 at 06:56:37PM -0800, Mark Davis wrote: >=20 > Yes, Keld's statement is completely inaccurate. True, there are a lot of information on character properties etc in unicode. Some of that info can be found in other ISO standards such as=20 ISO 14651 on sorting and ISO TR 14652 with an enhanced POSIX like=20 locales. What I meant is that the character table that defines the charset in IETF terms, is almost the same, and the UTF-8 spec is almost the same, and these are the specs that we probably will be using in=20 our enhanced mail spec. Best regards keld > Mark > __________________________________ > http://www.macchiato.com > ??? ??????????????????????????????????????????????????????????????? ??? >=20 > ----- Original Message -----=20 > From: "Adam M. Costello" <[email protected]> > To: <[email protected]> > Sent: Mon, 2004 Jan 05 17:15 > Subject: 10646 & Unicode >=20 >=20 > > > > Keld J=F8rn Simonsen <[email protected]> wrote: > > > > > 10646, not unicode, ... (as the technical differences are almost > > > negligible). > > > > I'm under the impression that the technical differences are quite gre= at, > > because Unicode includes a great deal of technical information that i= s > > absent from 10646 (but whatever does exist in 10646 is identical with= or > > at least compatible with Unicode). > > > > I haven't seen 10646 (it's too expensive), but does it include much m= ore > > than a code chart and specs for UTF-8 and UTF-16? Unicode includes a > > lot of character properties and algorithms for doing useful things ba= sed > > on those properties. See sections C.4 and C.7 of the Unicode standar= d: > > > > http://www.unicode.org/versions/Unicode4.0.0/appC.pdf > > > > Does 10646 include normalization forms (NFC, etc)? Those are likely = to > > be important in any effort to use the UCS in identifiers (like email > > addresses and web links). Does 10646 include case folding data? Tha= t > > is needed in any effort to use the UCS in case-insensitive identifier= s. > > > > AMC > >