Yeah, but I believe that at least Unicode has one of the four that they suggest
be used for non-locale specific comparisons (canonical decomposition form).
So pick that one for the core and provide the others (if necessary) as library
functions.
--
Mark Biggar
[EMAIL PROTECTED]
[EMAIL PROTECTED
Do we want a Normalization function here as well. If you have that you can use a
binary compare (at least for eq/ne).
--
Mark Biggar
[EMAIL PROTECTED]
> The charset vtable needs to handle get/set grapheme, get/set
> substring, up/down/titlecase, and (possibly) comparison. Charsets
> also ha
At 5:07 PM + 6/16/04, [EMAIL PROTECTED] wrote:
Yeah, but I believe that at least Unicode has one of the four that
they suggest
be used for non-locale specific comparisons (canonical decomposition form).
So pick that one for the core and provide the others (if necessary) as library
functions.
At 4:30 PM + 6/16/04, [EMAIL PROTECTED] wrote:
Do we want a Normalization function here as well. If you have that
you can use a binary compare (at least for eq/ne).
Yeah, we probably do. The question is always "Which normalization"
since there are at least four for Unicode and two for ISO-20
Okay, now that we've got the bytecode-visible stuff specified, I want
to spec the internals some, and start getting things migrated over to
it. (This should allow us to make ICU optional as well, for folks
that only want ASCII/Latin-x/EBCDIC enabled)
Once again, we're going with vtables, like t
