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.

Sign up for GitHub

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

Jump to bottom

Editorial: Document behaviour of U extension values locale slots #823

Merged
merged 4 commits into from
Sep 19, 2023
Merged

Editorial: Document behaviour of U extension values locale slots #823

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
cf845cd
Added non-normative note on the behaviour of the string stored in [[L…
ben-allen Aug 9, 2023
b133147
fixed grammatical error
ben-allen Aug 11, 2023
d34b943
Update spec/negotiation.html
ben-allen Aug 31, 2023
757bd64
added language indicating that extension sequences are only removed f…
ben-allen Aug 31, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion spec/negotiation.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -260,7 +260,7 @@ <h1>ResolveLocale ( _availableLocales_, _requestedLocales_, _options_, _relevant
</emu-alg>

<emu-note>
Non-normative summary: Two algorithms are available to match the locales: the Lookup algorithm described in RFC 4647 section 3.4, and an implementation dependent best-fit algorithm. Independent of the locale matching algorithm, options specified through Unicode locale extension sequences are negotiated separately, taking the caller's relevant extension keys and locale data as well as client-provided options into consideration. The abstract operation returns a record with a [[locale]] field whose value is the language tag of the selected locale, and fields for each key in _relevantExtensionKeys_ providing the selected value for that key.
Non-normative summary: Two algorithms are available to match the locales: the Lookup algorithm described in RFC 4647 section 3.4, and an implementation dependent best-fit algorithm. Independent of the locale matching algorithm, options specified through Unicode locale extension sequences are negotiated separately, taking the caller's relevant extension keys and locale data into consideration as well as the client-provided options. The abstract operation returns a Record with a field for each key in _relevantExtensionKeys_, containing the selected values for those keys. This Record also contains a [[locale]] field which stores the language tag, but with whatever U Extensions tags that are not in _relevantExtensionKeys_ removed. If a property is set by an option and also specified in the locale extension sequence, the value from the option is used to set the property's value and the overridden extension tag is removed from the string stored in [[locale]].
ben-allen marked this conversation as resolved.
Show resolved Hide resolved
</emu-note>
</emu-clause>

Expand Down
Loading