Hi Uri, I think you did not understand well the problem. Let me try to explain it in more details.
Nothing was changed with "ngettext" or "ngettext_lazy" in Django. The plural equation for Hebrew was changed on the Transifex platform and those changes reach Django each time we synchronize translations with Transifex (a script-driven process). Note that it was the case for some other languages too. The plural equation defines how many different plural forms can exist for any language. English has two, Arabic has six, etc. Apparently, someone discovered/decided that Hebrew can have 4 different plurals in certain cases, that's probably why Transifex changed it, but I cannot tell you more about the rationales. By reading the new Hebrew equation, it looks like the plural can be different if the number is 1, 2, (20, 30, 40, etc.), or anything else. The problem with Django, which is the object of #30439, is that Django is using only the plural equation of the core django.po file, so if you have several .po files with different plural equations, the plural may be wrong or can fallback to English. Typically in your case, the core Django po file has an equation with 4 plurals, while your Speedy.net po file has only 2, so when the translation infrastruction is looking for the 3rd or 4th form, it finds nothing and return the English string. You should be able to fix that by re-doing a makemessages in your project in a Django 2.2 environment, and you should find that your updated po file will have 4 plurals for each plural string (but then running your project with older Django versions can have translation problems again :-( ). Hopefully someone will have the time to prepare a patch to solve #30429 in order that plural string changes can be easily managed. Regards, Claude t <javascript:> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9d8ade17-3d6e-46dc-8ad7-a6b27de90593%40googlegroups.com.
