On Sat, Jan 11, 2020 at 3:38 AM Matemática A3K <[email protected]> wrote:
> Does anyone see any rationale, design or implementation problem in the > fix? Any comment is welcomed :) > https://github.com/django/django/pull/12280#issuecomment-575242878 We use Django 2.1 in Speedy Net and this issue has prevented us from upgrading to Django 2.2. I'm trying to understand this PR but it seems to me quite complicated. Will we be able to keep using 2 plural forms in Hebrew for our translations if this PR is accepted? Or will we have to convert our translations to 4 plural forms like is used in Django 2.2? For me it makes sense to use 2 plural forms (n==1, n!=1) because we don't need any complicated translations. I checked Django translations and almost/maybe in 100% of the Hebrew translations, 3 plural forms are identical. Do we have to convert our translations to 4 plural forms too? And if we want to keep using 2 plural forms in Hebrew, how do we do it while still using the latest version of Django? You can see my comments on #30439 and in the Django developers mailing list. Uri אורי -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CABD5YeE9PyYEObL4Lscw%2BZGWZYQTVDg80%2BL3_C3e6AW_5%3DfLXw%40mail.gmail.com.
