Intl.PluralRules()

[zbraniecki]

UPDATE: This proposal has advanced to stage 1, details here: https://github.com/caridy/intl-plural-rules-spec

cloned from: https://groups.google.com/forum/#!topic/javascript-globalization/3nFDf5al5hU

It would be very helpful for all l10n libraries to get CLDR plural forms into Intl API.

The proposed API could look like this:

var cardinal = new Intl.PluralFormat(‘en’, {style: ‘cardinal’});
console.log(cardinal.format(0)); // “other”
console.log(cardinal.format(1)); // “one”
console.log(cardinal.format(2)); // “other”

var ordinal = new Intl.PluralFormat(‘en’, {style: ‘ordinal’});
console.log(ordinal.format(11)); // “one”
console.log(ordinal.format(22)); // “two”
console.log(ordinal.format(33)); // “few”
console.log(ordinal.format(44)); // “other”

[caridy]

Makes sense, and it aligns well with some other proposals around this. Last time we talked about ICU messages, we ended up agreeing that better to do baby steps on this and get pluralization in place instead.

/cc @ericf, he has some ideas around this, and he was planning to champion the pluralization low level api.

[caridy]

Here is a backpointer to the discussion: https://groups.google.com/forum/#!topic/javascript-globalization/3nFDf5al5hU

[ericf]

@caridy Yeah @zbraniecki took this from the email thread. You guys both posted the same link to it :)

[caridy]

jaja

[zbraniecki]

The latest proposal that seems to address all comments so far:

var f = Intl.PluralForm(navigator.languages);

f.resolve(100); // 'other'
f.format(100, {
  one: 'comment',
  other: 'comments'
}); // 'comments'

I would say that the latter method should be lower priority for us. I like how simple it is, but I'm not sure if it would really be applicable for libraries that need it, while the former is definitely going to be directly applicable in multiple libraries I know of.

[caridy]

@zbraniecki let's keep the format with options out of the initial scope of this feature, we can discuss more later on.

[caridy]

Ok guys, finally got a chance to work on this, the initial proposal flush out:

https://github.com/caridy/intl-plural-form-spec

The generated spec [draft] is here:
https://rawgit.com/caridy/intl-plural-form-spec/master/index.html

I will work with @ericf next week for formalize the proposal and to see if we can formally presented (if we get a chance to add it to the agenda, which I doubt).

P.S.: I hate to post in groups and here.

[srl295]

Yes, just resolve plurals first… formatting is another step

I hate to post in groups and here

Just post a link to here and say follow up in github?

[srl295]

The spec looks great, very straightforward.

[rxaviers]

/cc @eemeli

[eemeli]

Thanks for the pointer @rxaviers. I added my comments to the mailing list thread.

Once the spec is ready-ish, I could probably pretty easily implement a polyfill for Intl.PluralRules from make-plural.js.