-
Notifications
You must be signed in to change notification settings - Fork 10
Dialect support? #20
Comments
@srl295 Just want to clarify, are you asking
The current draft of specification does not mandate the implementation to only output "Dutch (Belgium)", the implementation could choose to output "Flemish". It does not give the API caller to control the output. But is such control necessary? Shouldn't the implementation always try to output "Flemish"? |
@FrankYFTang coming back to this:
Yes, it's necessary. When choosing a language, it's common to sort the same language together: |
CLDR calls it CombineLanguage |
Could you first clarify which one you are asking about?
|
Yes, sorry for my terseness.
(1) is already what the implementation provides, so I was not commenting on that.
(2) is necessary for the reason mentioned above. Language selection UIs need to be able to choose "Dutch (Belgium)". |
FWIW the SpiderMonkey implementation (currently only available through the shell-only |
I put together a v2 repo on https://github.com/FrankYFTang/intl-displaynames-v2/ please move the future discussion there. |
This proposal reach Stage 4 in 2020 Sept TC39 meeting. Move this issue to tc39/proposal-intl-displaynames-v2#13 |
https://unicode.org/reports/tr35/tr35-general.html#Display_Name_Elements
example
nl-BE
= "Flemish", not just "Dutch (Belgium)"The text was updated successfully, but these errors were encountered: