Re: Proposal of code changes for l10n in FF3

Marek Stepien wrote:
> It should not be a problem at all with only one numeric variable; we'd
> just need to make sure that the "plural chooser" uses only the %d vars.
> [...]
> (the numbers represent: 0 - singular form, 1 - first plural form, 2 -
> second plural form, and so on)

And where do you envision coding the plural chooser ?

Is it some js, that must be added in the localisation, or an XPCOM 
component ? Maybe the nicest is an XPCOM component, that you can choose 
to code in js, or in low level language when that is more adapted.

Or, well maybe we should include in the i18n code a table driven plural 
chooser, and the l10n provides the tables so that we solve the 
performance problem. If it's *really* complex, there could be a way by 
which the localisation provide it's own XPCOM implementation to call.

Copying i18n.