Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

Dialect support? #20

Closed
srl295 opened this issue Feb 21, 2019 · 8 comments
Closed

Dialect support? #20

srl295 opened this issue Feb 21, 2019 · 8 comments
Labels
enhancement New feature or request Later For future version to consider, NOT now.

Comments

@srl295
Copy link
Member

srl295 commented Feb 21, 2019

https://unicode.org/reports/tr35/tr35-general.html#Display_Name_Elements

example nl-BE = "Flemish", not just "Dutch (Belgium)"

@FrankYFTang
Copy link
Collaborator

FrankYFTang commented Mar 7, 2019

@srl295 Just want to clarify, are you asking

  1. the implementation to output "Flemish" for "nl-BE" instead of "Dutch (Belgium)", or
  2. the specification to allow the API to allow both "Flemish" and "Dutch (Belgium)" could be output for "nl-BE" and demand a method to control which one being output?

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 FrankYFTang added the enhancement New feature or request label Jun 14, 2019
@FrankYFTang FrankYFTang added the Later For future version to consider, NOT now. label Sep 24, 2019
@srl295
Copy link
Member Author

srl295 commented May 13, 2020

@FrankYFTang coming back to this:

is such control necessary? Shouldn't the implementation always try to output "Flemish"?

Yes, it's necessary. When choosing a language, it's common to sort the same language together:

  • mac example
    image

@srl295
Copy link
Member Author

srl295 commented May 13, 2020

CLDR calls it CombineLanguage

@FrankYFTang
Copy link
Collaborator

Could you first clarify which one you are asking about?

  1. the implementation to output "Flemish" for "nl-BE" instead of "Dutch (Belgium)", OR
  2. the specification to allow the API to allow both "Flemish" and "Dutch (Belgium)" could be output for "nl-BE" and demand a method to control which one being output?

@srl295
Copy link
Member Author

srl295 commented May 16, 2020

Could you first clarify which one you are asking about?

Yes, sorry for my terseness.

  1. the implementation to output "Flemish" for "nl-BE" instead of "Dutch (Belgium)", OR

(1) is already what the implementation provides, so I was not commenting on that.

  1. the specification to allow the API to allow both "Flemish" and "Dutch (Belgium)" could be output for "nl-BE" and demand a method to control which one being output?

(2) is necessary for the reason mentioned above. Language selection UIs need to be able to choose "Dutch (Belgium)".

@anba
Copy link
Collaborator

anba commented May 23, 2020

FWIW the SpiderMonkey implementation (currently only available through the shell-only addIntlExtras helper), defaults to UDISPCTX_STANDARD_NAMES per the recommendation voiced in https://unicode-org.atlassian.net/browse/CLDR-13430. So for nl-BE, SpiderMonkey returns "Dutch (Belgium)".

@FrankYFTang
Copy link
Collaborator

I put together a v2 repo on https://github.com/FrankYFTang/intl-displaynames-v2/ please move the future discussion there.

@FrankYFTang
Copy link
Collaborator

This proposal reach Stage 4 in 2020 Sept TC39 meeting. Move this issue to tc39/proposal-intl-displaynames-v2#13

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request Later For future version to consider, NOT now.
Projects
None yet
Development

No branches or pull requests

3 participants