Plural tags and counts for i18next about translate HOT 5 CLOSED

As Weblate supports v4 now as well, I've added hint about plurals to our docs: WeblateOrg/weblate@bf7db3c

from translate.

The code states it is based on https://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html, but that is not true as well.

Farsi mentioned in WeblateOrg/weblate#8625 has two plurals there (same as in CLDR), but only one in i18next. Maybe this is i18next bug in the end?

from translate.

Okay, I think it's a bug in i18next, there were already similar in the past, see i18next/i18next#1607

from translate.

Okay, I think it's a bug in i18next, there were already similar in the past, see i18next/i18next#1607

Ok, thanks! I'll open an issue there, then!

from translate.

It turns out that i18next decided to build their own plural rules instead of relying on CLDR like nearly everybody else. Because of that plural tags differ for some language in translate-toolkit and the original code.

I looked more into this. They moved to the v4 format exactly for that reason.

So now, the v3 plural rules are set into the stone (and forever broken) and the v4 rules depends on the Intl Javascript API, which is maintained by upstream (NodeJS/Chromium/Firefo/etc...) and change according to the CLDR.

from translate.