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

Update NumberFormat.prototype.useGrouping test for CLDR 45 #4061

Merged
merged 1 commit into from
Jul 24, 2024

Conversation

trflynn89
Copy link
Contributor

In CLDR 45, in the en-IN locale, the compact thousands symbol changed from 'T' to 'K' after a survey was conducted in India:

unicode-org/cldr@b8d4472

@Ms2ger
Copy link
Contributor

Ms2ger commented Apr 19, 2024

I wonder if we should allow both

Copy link
Contributor

@ptomato ptomato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been open for quite a long time, so implementations have had time to adapt to CLDR 45. In general I prefer not to test against hardcoded internationalization output, but given the age of this PR I'll suggest that we just land it. If that causes problems for implementations that haven't adapted to the CLDR change, we can then do something more complicated to allow both variations.

In CLDR 45, in the en-IN locale, the compact thousands symbol changed
from 'T' to 'K' after a survey was conducted in India:

unicode-org/cldr@b8d4472
@ptomato ptomato merged commit d8aa2e4 into tc39:main Jul 24, 2024
8 checks passed
@trflynn89 trflynn89 deleted the cldr45 branch July 31, 2024 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants