Repository navigation
spec: draft LocaleMatcher semantics and best-fit design - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft LocaleMatcher semantics using current ECMA-402 operations: input validation, canonicalization, extensions, and explicit fallback.
Best fit remains implementation-defined. Design notes sketch a separate selection algorithm without requiring CLDR/ICU data, review open issues #2, #3, #4, #6, #8, and outline compatibility and conformance work. These are draft positions, not committee consensus.
Validation: strict ecmarkup build, formatter, rendered references, and diff checks. Pinned build tooling runs on pushes and PRs; generated output is committed only on main.