Skip to content

Editorial: Clarify that "well-formed language tag" does not imply unicode_bcp47_locale_id well-formedness - #1048

Merged
gibson042 merged 1 commit into
tc39:mainfrom
gibson042:gh-1046-well-formed-language-tag
Oct 8, 2026
Merged

gibson042 merged 1 commit into
tc39:mainfrom
gibson042:gh-1046-well-formed-language-tag

Conversation

@gibson042

Copy link
Copy Markdown
Member

Fixes #1046

As noted there, "en-u-ca-buddhist-ca-islamic" and other inputs with duplicate ukeys are accepted (and must continue to be). IsWellFormedLanguageTag therefore does not ensure conformance with the well-formedness constraints of a unicode_bcp47_locale_id, but rather with a slightly weaker set of constraints that are specific to ECMA-402 that this PR describes in a new note.

@gibson042
gibson042 requested review from eemeli and removed request for ben-allen October 5, 2026 21:49
Comment thread spec/locales-currencies-tz.html Outdated
@gibson042
gibson042 force-pushed the gh-1046-well-formed-language-tag branch from 9c7a1dc to a18b136 Compare October 8, 2026 16:57
@gibson042
gibson042 merged commit 30c4d13 into tc39:main Oct 8, 2026
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.

IsWellFormedLanguageTag doesn't match well-formedness from UTS 35 for duplicate ukey or tkey values

2 participants