i18next uses suffixes for plural forms, and always supports the _zero
suffix.
From i18next documentation
We provide the ability to have special translation for
{count: 0}
, so that a more natural language can be used. If the count is 0, and a_zero
entry is present, then it will be used instead of the language plural suffix.
When using JSON i18next files in Crowdin, the only workaround I found to support these _zero
entries is to create custom languages. However this doesn’t quite work as the _zero
form from the source file won’t be displayed, and it doesn’t look like a custom language can be used for the source.
I think _zero
should always be an option, regardless of the source/target language.
I’d be happy to try any suggested workaround, but from my point of view this is a bug/missing feature of the file format support.
Thanks for the help!
Matthieu