Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify CollapseNumberRange AO #940

Merged
merged 1 commit into from
Nov 12, 2024
Merged

Conversation

ben-allen
Copy link
Contributor

This makes the following editorial changes to Intl.NumberFormat's CollapseNumberRange AO:

Fix #935

This makes the following editorial changes to `Intl.NumberFormat`'s
`CollapseNumberRange` AO:

* Make `CollapseNumberRange` take an `Intl.NumberFormat` as a parameter
to enable locale-specific modifications of the `result` list.

* Explicitly state that `CollapseNumberRange` can potentially add
spacing characters, as in the LDML `Range Pattern Processing`
instructions. See https://unicode-org.github.io/cldr/ldml/tr35-numbers.html#Range_Pattern_Processing
@ben-allen ben-allen merged commit 0825ad7 into tc39:main Nov 12, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Intl.NumberFormat.formatRange seems to missing the Range Pattern Processing step compared to LDML
3 participants