Complicated plurals don't work for me about i18next-node HOT 7 CLOSED

key_plural_0 would be for a zero based specialform in english - but english has no specialform for 0 (zero uses the regular plural).

i18next supports the plural like in given language and doesn't lookup special cases. You can solve what you try with context http://i18next.com/pages/doc_features.html#context

{
    "key_zero": "__count__ like", /* should never be called as zero uses plural form */
    "key_zero_plural": "No likes",
    "key_many": "__count__ like",
    "key_many_plural": "__count__ likes",
}

i18n.t('key', {
  count: 0, /* as normal */
  context: (count !== 0) ? 'many' : 'zero'
});

from i18next-node.

With this translation .json

{
    "key": "__count__ like",
    "key_plural": "__count__ likes",
    "key_plural_0": "No likes",

    "simple": "__count__ like",
    "simple_plural": "__count__ likes"
}

The special case for 0 doesn't work. I was expecting:

No likes
1 like
2 likes

Instead of:

0 likes
1 like
2 likes

from i18next-node.

I still can't manage to make plural form work in any language from Jade template.

.text=t("key", {count : 0}) // displays : default
.text=t("key", {count : 1}) // displays : default
.text=t("key", {count : 2}) // displays : default

{
"key" : "default"
"key_zero": "you have no foo"
"key_1_plural": "you have count foo",
"key_plural": "you have count foos",
}

I understand that plural forms are specific to languages but it looks like i still don't understand how it works.

from i18next-node.

english has only singular and plural form -> so you don't need to suffix the keys for en. Only locales with more than one plural form (or zero) need to be suffixed.

from i18next-node.

I completely misunderstood the plural functionality, but your workaround is perfect. Thanks!

from i18next-node.

glad we found a solution. if you encounter any other issue, just let me know.

from i18next-node.

looks strange to me:

// having
{
"key" : "default"
"key_plural": "you have __count__ foos",
}

// it should
.text=t("key", {count : 0}) // should displays : you have 0 foos
.text=t("key", {count : 1}) // displays : default (this one is ok)
.text=t("key", {count : 2}) // should displays : you have 2 foos

the key_zero and key_1_plural will only be accessed if you use the respecting keys (key_zero, key_1) or add the context option ( context = zero, context = 1).

when i run the tests in the client repository https://github.com/jamuhl/i18next/blob/master/spec/translate/translate.plurals.spec.js it works correctly...wondering where the problem with 0 and 2 comes from

from i18next-node.