#30439: Translations issues on Django upgrade due to unexpected changes in
plural
forms
-------------------------------------+-------------------------------------
Reporter: Michal Čihař | Owner: Claude
| Paroz
Type: Bug | Status: assigned
Component: | Version: 2.2
Internationalization |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by אורי):
Replying to [comment:42 Carlton Gibson]:
> Hi Claude, thanks for the PR. Pending testing/confirmation from Michal,
please uncheck ''Needs documentation'' when you're ready.
If PR [https://github.com/django/django/pull/12332 #12332] is accepted,
will it be possible for you guys to apply it to Django 2.2 as well?
Especially since translations (for example in Hebrew) break / stop working
when upgrading Django from 2.1 to 2.2, and it seems that this PR solves it
(translations work). Or is it against your policy to apply such a PR to a
Django version such as 2.2? I would very much prefer it if you guys apply
this PR to Django 2.2, then to have to fork Django and install it from
fork in production, where I will have to apply this PR to any future
version of Django you will release. Or on the other hand keep using Django
2.1 which is obsolete.
--
Ticket URL: <https://code.djangoproject.com/ticket/30439#comment:43>
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.fe25368c221c684552b0d93039037b04%40djangoproject.com.
