On Fri, 8 Jun 2001, Jarkko Hietaniemi wrote:
An interesting article in the July DDJ) in the Algorithm Alley:
Fast and Small Resizable Arrays, presents a datastructure that
promises just what the subject says.
The first thing I thought of after reading the article was use less
memory... I
At 05:20 PM 6/7/2001 +, Nick Ing-Simmons wrote:
Dan Sugalski [EMAIL PROTECTED] writes:
It does bring up a deeper issue, however. Unicode is, at the moment,
apparently inadequate to represent at least some part of the asian
languages. Are the encodings currently in use less inadequate?
At 10:41 PM 6/7/2001 -0400, Buddha Buck wrote:
Nick Ing-Simmons [EMAIL PROTECTED] writes:
Dan Sugalski [EMAIL PROTECTED] writes:
It does bring up a deeper issue, however. Unicode is, at the moment,
apparently inadequate to represent at least some part of the asian
languages. Are the
I can't really believe that this would be a problem, but if they're integrated
alphabets from different locales, will there be issues with sorting (if we're
not planning to use the locale)? Are there instances where like characters were
combined that will affect the sort orders?
Grant M.
I can't really believe that this would be a problem, but if they're
integrated alphabets from different locales, will there be issues
with sorting (if we're not planning to use the locale)? Are there
instances where like characters were combined that will affect the
sort orders?
Another example is the chinese has no definite
sorting order, period. The commonly used scheme are
phonetic-based or stroke-based. Since many characters
have more than one pronounciations (context sensitive)
and more than one forms (simplified and traditional).
So if we have a mix content
At 11:29 AM 6/8/2001 -0700, Hong Zhang wrote:
If this is the case, how would a regex like ^[a-zA-Z] work (or other,
more
sensitive characters)? If just about anything can come between A and Z,
and
letters that might be there in a particular locale aren't in another
locale,
then how will
The A-Z syntax is really a shorthand for All the uppercase letters.
(Originally at least) I won't argue the problems with sorting various sets
of characters in various locales, but for regexes at least it's not an
issue, because the point isn't sorting or ordering, it's identifying
Dan Sugalski [EMAIL PROTECTED] writes:
At 05:20 PM 6/7/2001 +, Nick Ing-Simmons wrote:
One reason perl5.7.1+'s Encode does not do asian encodings yet is that
the tables I have found so far (Mainly Unicode 3.0 based) are lossy.
Joy. Hopefully by the time we're done there'll be a full
Nicholas Clark [EMAIL PROTECTED] writes:
What happens if unicode supported uppercase and lowercase numbers?
[I had a dig about, and it doesn't seem to mention lowercase or
uppercase digits. Are they just a typography distinction, and hence not
enough to be worthy of codepoints?]
Damned if
What happens if unicode supported uppercase and lowercase numbers?
[I had a dig about, and it doesn't seem to mention lowercase or
uppercase digits. Are they just a typography distinction,
and hence not
enough to be worthy of codepoints?]
Damned if I know; I didn't know there even
11 matches
Mail list logo
