You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let list be a List of 1 or more collation identifiers, which must be String values conforming to the type sequence from UTS 35 Unicode Locale Identifier, section 3.2, sorted in descending preference of those in common use in the locale for string comparison.
Intl.Collator suppresses "standard" and "search" collations, because they're handled through the "usage" property. I'm not sure the same reasoning also applies to CollationsOfLocale(), especially because the current spec text describes that the commonly used collations should be returned, which normally do include "standard" and "search".
However we decide to handle those two collation identifiers, we should definitely explicitly mention them in CollationsOfLocale().
The text was updated successfully, but these errors were encountered:
Address #31
This PR is logical because in https://tc39.es/ecma402/#sec-intl-collator-internal-slots
```
The values "standard" and "search" must not be used as elements in any [[SortLocaleData]].[[<locale>]].[[co]] and [[SearchLocaleData]].[[<locale>]].[[co]] list.
```
Address #31
This PR is logical because in https://tc39.es/ecma402/#sec-intl-collator-internal-slots
```
The values "standard" and "search" must not be used as elements in any [[SortLocaleData]].[[<locale>]].[[co]] and [[SearchLocaleData]].[[<locale>]].[[co]] list.
```
Per https://tc39.es/proposal-intl-locale-info/#sec-hour-cycles-of-locale:
Intl.Collator
suppresses "standard" and "search" collations, because they're handled through the "usage" property. I'm not sure the same reasoning also applies toCollationsOfLocale()
, especially because the current spec text describes that the commonly used collations should be returned, which normally do include "standard" and "search".However we decide to handle those two collation identifiers, we should definitely explicitly mention them in
CollationsOfLocale()
.The text was updated successfully, but these errors were encountered: