10646 & Unicode

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 great,
because Unicode includes a great deal of technical information that is
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 more
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 based
on those properties.  See sections C.4 and C.7 of the Unicode standard:

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?  That
is needed in any effort to use the UCS in case-insensitive identifiers.

AMC