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

Use of CanonicalizeUnicodeLocaleId #1084

Open
aphillips opened this issue May 15, 2023 · 2 comments · May be fixed by #1101
Open

Use of CanonicalizeUnicodeLocaleId #1084

aphillips opened this issue May 15, 2023 · 2 comments · May be fixed by #1101
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@aphillips
Copy link
Contributor

lang member
https://w3c.github.io/manifest/#lang-member

Set manifest["lang"] to the result of calling the CanonicalizeUnicodeLocaleId abstract operation with json["lang"].

The instructions on processing the lang member are inconsistent with the description of what a lang member can contain. The ECMA-402 function CanonicalizeUnicodeLocaleID is invoked and this results in a variety of potential changes to a few otherwise-valid values. This is probably the right thing to do when actually consuming the lang member's value (particularly with Intl.Locale and friends in JavaScript), but its sudden appearance buried in the processing instructions makes this surprising. This suggests that lang should actually be defined as a Unicode Locale ID??

It's not clear if referencing Unicode Locale IDs is the right thing for the manifest spec to do, since the manifest is mainly concerned with transmitting data values, not actually performing runtime processing.

@aphillips aphillips added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label May 15, 2023
@marcoscaceres
Copy link
Member

I guess we just want to make sure we always get a canonical language tag.

@christianliebel christianliebel linked a pull request Jul 2, 2024 that will close this issue
4 tasks
christianliebel added a commit that referenced this issue Jul 6, 2024
We can leave this to the OS, which will simply ignore invalid language tags.
@christianliebel
Copy link
Member

In #1101, I removed mentioning specific algorithms altogether.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants