I'm afraid it's not quite so simple. The Internationalization API spec defines
localeCompare() as a wrapper around Intl.Collator.prototype.compare, so to make
normalization mandatory for localeCompare, we'd have to make it mandatory for
Collator as well. I'd like to get some input from implement
Norbert--
> The ECMAScript Internationalization API Specification currently has
> normalization as an optional feature in collation. However, it requires that
> the compare function "return 0 when comparing Strings that are considered
> canonically equivalent by the Unicode standard". Canonical
The test is at
http://norbertlindenberg.com/ecmascript/ESTest.html (and .js).
The strings I used are:
["o\u0308", "ö"],
["ä\u0323", "a\u0323\u0308"], // requires reordering
["a\u0308\u0323", "a\u0323\u0308"], // requires reordering
["ạ\u0308", "a\u0323\u0308"],
["ä\u0306", "a\u0308\u0306"],
["ă\u0
On Tue, Jun 19, 2012 at 12:36 AM, Norbert Lindenberg <
ecmascr...@norbertlindenberg.com> wrote:
> The ECMAScript Internationalization API Specification currently has
> normalization as an optional feature in collation. However, it requires
> that the compare function "return 0 when comparing Strin
The ECMAScript Internationalization API Specification currently has
normalization as an optional feature in collation. However, it requires that
the compare function "return 0 when comparing Strings that are considered
canonically equivalent by the Unicode standard". Canonical equivalence, I
th
5 matches
Mail list logo
