Skip to content

Commit

Permalink
Editorial: Document ResolveLocale handling of -u- locale extensions v…
Browse files Browse the repository at this point in the history
…s. options
  • Loading branch information
ben-allen authored Sep 19, 2023
1 parent 8ad694a commit 4dbe8df
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion spec/negotiation.html
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 of the selected locale with Unicode locale extension sequence <code>key</code> subtags restricted to those in _relevantExtensionKeys_. If an extension's value is specified in the Unicode locale extension sequence and a different value for that extension is specified in an option, the value from the option is used to set the value of the corresponding field and the overridden extension keyword (the <code>key</code> subtag along with any immediately following <code>type</code> subtags and associated separators) is removed from the string stored in [[locale]].
</emu-note>
</emu-clause>

Expand Down

0 comments on commit 4dbe8df

Please sign in to comment.