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

CalendarsOfLocale, CollationsOfLocale, and NumberingSystemsOfLocale should return canonical identifiers #32

Closed
anba opened this issue May 14, 2021 · 2 comments

Comments

@anba
Copy link
Contributor

anba commented May 14, 2021

CalendarsOfLocale, CollationsOfLocale, and NumberingSystemsOfLocale should return canonical identifiers.

For example "gb2312" instead of "gb2312han" for new Intl.Locale("zh").collations.

@FrankYFTang
Copy link
Collaborator

Here is the current spec text said

Let list be a List of 1 or more unique calendar identifiers, which must be lower case 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 for date and time formatting in locale.

I blieve the "conforming to the type sequence from UTS 35 Unicode Locale Identifier, section 3.2" part already address the issue of "canonical identifiers". For example - "gb2312han" will not fit that clause and won't be return. I do not believe we need to add any more word for this.

I am closing this. Please feel free to reopen if you think the current spec text is still not need clear enough.

@anba
Copy link
Contributor Author

anba commented Aug 31, 2021

I've only used "gb2312han" as an example to point out the V8 bug fixed in https://bugs.chromium.org/p/v8/issues/detail?id=11887.

There are still other cases where not requiring canonical identifiers can result in cross-compatibility issues. For example we should require that "islamicc" is canonicalised to "islamic-civil" and that "ethiopic-amete-alem" is canonicalised to "ethioaa".

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

No branches or pull requests

2 participants