Locale.GetND should return singular default when N=1 about gotext HOT 2 CLOSED

@alexedwards I've been looking into this issue, and while it's a bug, the solution is more complex than just N=1.

What's happening here is that the Locale object you're using doesn't have the Domain (Po object) you're requesting loaded, so it defaulted to the plural.
That said, the current implementation was using the n == 1 rule to identify singular cases, and that's kind of incorrect, because it would depend on the plurals definition from the .po file.

So I'm working on a solution in the Po object that will fallback to the corresponding default value based on the plural forms definitions in the .po file.
When it fallbacks to an non-existing translation string, but on an existing domain (.po file) it will use this new approach.
Otherwise, as if the domain isn't loaded and it doesn't knows how plural definitions are, it will fallback using the western n == 1 rule, just to make a convention here.

I'll be pushing a fix to master branch soon.

from gotext.

Thanks for the time looking into this and the fast fix. I really appreciate it 👍

from gotext.