Shane F. Carr

The current pattern on how to do this is to pass NumberFormat options into the PluralRules constructor: ```javascript const nf = new Intl.NumberFormat("fr-FR", { notation: "compact" }); const pr =...

2.3e6 in fr-FR: "2 300 000 vues" (plural form "other") But when compact notation is used: "2,3 millions de vues" (plural form "many")

formatSelect does not add any new functionality; it just makes the existing functionality more discoverable, understandable, and efficient. Use cases are not a consideration.

I plan to address this as part of my new proposal Intl.NumberFormat V3. https://github.com/sffc/proposal-intl-numberformat-v3

This isn't a feature; it's a refactoring of existing feature. You can refer back to the PluralRules proposal for the full list of use cases. In message formatting, you generally...

**Unintuitive:** Previous discussions regarding confusion over Intl.PluralRules behavior: #373, #365, https://github.com/tc39/proposal-unified-intl-numberformat/issues/86. I have also seen users simply unaware that fraction digit settings need to be passed to Intl.PluralRules in order...

Bikeshed: 1. Intl.NumberFormat.prototype.formatSelect returning `{ string, pluralForm }` - Pros: All features in one place; easy to use correctly; works nicely with formatRange - Cons: Doubles number of terminal methods,...

We decided in the 2020-04-23 meeting to table this issue, because none of the proposed options solve the problem completely. We will still require documentation, even if we add new...

@eemeli has a proposal that fixes this for string inputs: https://github.com/eemeli/proposal-intl-keep-trailing-zeros

I'm not sure if the zone variant calculator is enough. It is only supposed to know about when a time zone switched between metazone or zone variants with a broad...