Open
Description
This is an issue fork out from @anba's comment in the review of
tc39/proposal-intl-locale-info#83
During 2024-07-18, TG2 believe the patch @anba suggested has other undesireable side effect, such as "fr-u-ca-hebrew" may not return the right result .
What @anba suggest is
- 1. Let _r_ be a record whose fields are defined by <emu-xref href="#table-locale-weekinfo-record"></emu-xref>, with values based on _locale_.
+ 1. Let _languageId_ be the longest prefix of _locale_ matched by the <code>unicode_language_id</code> Unicode locale nonterminal.
+ 1. Let _r_ be a record whose fields are defined by <emu-xref href="#table-locale-weekinfo-record"></emu-xref>, with values based on _languageId_.
but that remove not just 'rg' but also 'ca'
The question is how should we address the issue that we want to make sure right now we will not listen to 'rg' but will still respect to 'ca'.