#30439: Translations issues on Django upgrade due to unexpected changes in
plural
forms
--------------------------------------+------------------------------------
Reporter: Michal Čihař | Owner: Rodrigo
Type: Bug | Status: assigned
Component: Internationalization | Version: 2.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by אורי):
Replying to [comment:22 Michal Čihař]:
> The earlier mentioned example of
[https://hosted.weblate.org/languages/he/#information Hebrew] can be seen
on our public hosting service - 25% of translations use simple two plurals
and 75% use more complex four plurals. Both are correct and in many cases
the one with two plural forms is working well at it makes it easier for
translators.
Actually I checked Django translations in Hebrew and it seems to me that
maybe/almost in 100% of the translations where there are 4 plural forms,
the 3 last plural forms are identical. In reality I think in about 80% to
90% of the cases, 2 plural forms are enough. I don't see any reason why to
add 2 additional plural forms to our translations (in Speedy Net), if they
are identical to the second plural form we already have. But if we must
have 4 plural forms in Hebrew, at least I would expect Django to add the 2
additional plural forms in a correct way when I upgrade Django to 2.2.
The best solution for me would be, if I can keep using 2 plural forms for
Hebrew on Speedy Net, without relating to how many plural forms Django is
using for its own translations.
--
Ticket URL: <https://code.djangoproject.com/ticket/30439#comment:29>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates/063.34170add421b4fa659c1dd05db79e075%40djangoproject.com.
