Comment #22 on issue 459 by [email protected]: localeCompare
implementation differs from other browsers
http://code.google.com/p/v8/issues/detail?id=459
the fact that locale affects this is only half the problem, the other is
that it isnt currently using any ICU collation, just using the character
values (as mentioned above the raw UTF16 character value), thats why "
"a".localeCompare("A");
32
in chrome, whereas in firefox
"a".localeCompare('A');
-1
It seems like it would be hard to implement a subset that implemented
collation properly even for just the ascii character range without just
implementing the full unicode collation algorithm *, which would be a
pretty massive job, if anyone has pointers / suggestions I am open to them
though, the app I am building requires ICU collation, even if its only a
single locale that is implemented
* http://www.unicode.org/reports/tr10/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
