@@ -40,48 +40,6 @@ or can be resolved to a string without error.
4040For other values, a _Bad Option_ error is emitted
4141and the `u:id` _option_ and its _option value_ are ignored.
4242
43- #### `u:locale`
44-
45- > [!IMPORTANT]
46- > This _option_ has a status of **Draft**.
47- > It is proposed for inclusion in a future release and is not Stable.
48-
49- Implementations MAY support this option.
50-
51- Replaces the _locale_ defined in the _function context_ for this _expression_.
52-
53- A comma-delimited list consisting of
54- well-formed [BCP 47](https://www.rfc-editor.org/rfc/bcp/bcp47.txt)
55- language tags,
56- or an implementation-defined list of such tags.
57-
58- If this _option_ is set on _markup_, a _Bad Option_ error is emitted
59- and the `u:locale` _option_ and its _option value_ are ignored.
60-
61- During processing, the `u:locale` _option_
62- MUST be removed from the resolved mapping of _options_
63- before calling the _function handler_.
64-
65- Values matching the following ABNF are always accepted:
66- ```abnf
67- u-locale-option = unicode_bcp47_locale_id *(o "," o unicode_bcp47_locale_id)
68- ```
69- using ` unicode_bcp47_locale_id ` as defined for
70- [ Unicode Locale Identifier] ( https://unicode.org/reports/tr35/tr35.html#unicode_bcp47_locale_id ) .
71-
72- Implementations MAY support additional language tags,
73- such as private-use or grandfathered tags,
74- or tags using ` _ ` instead of ` - ` as a separator.
75- When the value of ` u:locale ` is set by a _ variable_ ,
76- implementations MAY support non-string values otherwise representing locales.
77-
78- Implementations MAY emit a _ Bad Option_ error
79- and MAY ignore the ` u:locale ` _ option_ and _ option value_ as a whole
80- or any of the entries in the list of language tags.
81- This might be because the locale specified is not supported
82- or because the language tag is not well-formed,
83- not valid, or some other reason.
84-
8543#### `u:dir`
8644
8745Implementations SHOULD support this option.
0 commit comments