Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Issue 459 in v8: localeCompare implementation differs from other browsers
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
codesite-nore...@google.com  
View profile  
 More options Apr 18 2012, 10:15 pm
From: codesite-nore...@google.com
Date: Thu, 19 Apr 2012 02:15:31 +0000
Local: Wed, Apr 18 2012 10:15 pm
Subject: Re: Issue 459 in v8: localeCompare implementation differs from other browsers

Comment #22 on issue 459 by d...@arandomurl.com: 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/


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.