Timothy Flynn e74e8381d5 LibJS: Allow "approximately" results to differ in plural form ... This is a normative change in the Intl.NumberFormat V3 spec. See: 08f599b Note that this didn't seem to actually affect our implementation. The Unicode spec states: https://www.unicode.org/reports/tr35/tr35-53/tr35-numbers.html#Plural_Ranges "If there is no value for a <start,end> pair, the default result is end" Therefore, our implementation did not have the behavior noted by the issue this normative change addressed: const pr = new Intl.PluralRules("en-US"); pr.selectRange(1, 1); // Is "other", should be "one" Our implementation already returned "one" here because there is no such <start=one, end=one> value in the CLDR for en-US. Thus, we already returned the end value of "one".		2023-01-30 14:10:07 -05:00
..
PluralRules.@@toStringTag.js	LibJS: Implement a nearly empty Intl.PluralRules object	2022-01-28 19:38:47 +00:00
PluralRules.js	LibJS: Move resolution of some Intl.NumberFormat options to a common AO	2023-01-30 12:19:14 -05:00
PluralRules.prototype.resolvedOptions.js	LibJS: Move resolution of some Intl.NumberFormat options to a common AO	2023-01-30 12:19:14 -05:00
PluralRules.prototype.select.js	LibLocale+LibJS: Update to CLDR version 42.0.0	2022-10-25 10:10:39 +01:00
PluralRules.prototype.selectRange.js	LibJS: Allow "approximately" results to differ in plural form	2023-01-30 14:10:07 -05:00
PluralRules.supportedLocalesOf.js	LibJS: Implement Intl.PluralRules.supportedLocalesOf	2022-01-28 19:38:47 +00:00