| 09:36 | <hsivonen> | Does there exist stated design rationale for why Intl.Collator (which, unlike many other APIs, doesn't format anything) falls back to the host locale instead of falling back to und? Considering that the root collation is more likely to be valid for a language that isn't explicitly listed in CLDR than a non-root host-language collation, the specified behavior seems unfortunate. Moreover, it's bad that the distinction isn't visible in the typical CI locale of en-US. |
| 12:36 | <littledan> | Everything in Intl falls back to the host locale… I think that’s the extent of the rationale. |
| 12:37 | <littledan> | If we wanted to work on Intl.Collator, we should probably address the thing where the design forces a bunch of recalculation of the collation key to do any sorting… |
| 14:39 | <sffc> | > Moreover, it's bad that the distinction isn't visible in the typical CI locale of en-US. Can you check the resolved options to get the locale? |