Shane F. Carr comments

Results 1881 comments of


                                            Shane F. Carr

ships the entire payload requirement

@ben-allen will write a PR to add text to the spec describing the requirement.

LookupMatcher should retain Unicode extension keywords in DefaultLocale

To be clear: DefaultLocale does not have Unicode extensions. It is always a baseName (LSRV). Therefore, if a locale has a Unicode extension sequence, but the baseName is not in...

Define sort order of "pluralCategories" array

TG1 notes: https://github.com/tc39/notes/blob/main/meetings/2021-10/oct-26.md#specifying-order-of-lists-returned-from-intl-apis We should do the following: 1. Document in the style guide that we should indeed specify the order 2. Document that the default order should be lexicographic...

Define sort order of "pluralCategories" array

@ben-allen to make the second PR for the PluralRules.

Relax the ordering requirement on formatRange and selectRange functions

Confirmed that both Intl.NumberFormat and Intl.DateTimeFormat support arguments in both orders.

Intl.Segmenter with URLs, email addresses, and acronyms

CLDR issue: https://unicode-org.atlassian.net/browse/CLDR-15767 Another: https://unicode-org.atlassian.net/browse/CLDR-15839

Forbid underscores in DisplayNames identifiers

Confirmed that this appears to have been fixed by #647

Formalize plan for ECMA-402 updates dependent on UTS 35

Discussion: be explicit in the spec that sections which depend on CLDR/Unicode are only kept in sync on a best-effort basis. These are two separate specs with two different lifecycles.

Editorial: Start all fields and slots with an uppercase code point

Happy to let the editors decide whether to either fix this issue or close this issue.

Detecting directionality from script type (or from a language associated with a script)

This is being addressed by the Intl Locale Info Proposal https://github.com/tc39/proposal-intl-locale-info?tab=readme-ov-file#text-information