String.prototype.[de]normalize and .isCharXxx are needed

Herby Vojčík herby at
Wed Jan 18 02:45:22 PST 2012

Norbert Lindenberg wrote:
> In order to get version 1 of the Globalization API done and into the
> hands of users, we're no longer considering new functionality for
> this version. On the other hand, string comparison (collation) is
> already included in this version, and the sensitivity option lets you
> choose whether it should be sensitive to minor differences such as
> accents. See

It was just one simple use-case. I want to do other things for which 
splitting accents and base character and their differentiation is needed 
(as for their differentiation, it should not be a big deal, but 
normalization/denormalization is critical).

> Norbert


> On Jan 17, 2012, at 4:06 , Herby Vojčík wrote:
>> Norbert Lindenberg wrote:
>>> Nothing planned at this point. Unicode normalization would be a
>>> natural candidate for the Globalization API, but it's not in
>>> scope for version 1. Support for Unicode character properties
>>> probably
>> Maybe it could be added?
>>> should be part of regular expressions, as it is in Perl, PHP,
>>> Java, and other platforms; there was a proposal for ES4 [1], but
>>> it hasn't been taken up for ES5 or Harmony.
>> Well, string comparision sans accents is a sensible use case. To do
>> it via Unicode normalization and then removing all accents is
>> straightforward. Should it (the character properties, however done)
>> not be raised?
>>> [1]

More information about the es-discuss mailing list