#30439: Translations issues on Django upgrade due to unexpected changes in
plural
forms
-------------------------------------+-------------------------------------
Reporter: Michal Čihař | Owner: Claude
| Paroz
Type: Bug | Status: closed
Component: | Version: 2.2
Internationalization |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by אורי):
Hi, I just want to say that I upgraded Django to 2.2.12 in
[https://github.com/speedy-net/speedy-net Speedy Net] and then upgraded
again to 3.0.5, and everything works as expected. I didn't change anything
in our translation files and they are still using the old plural forms
formula like before (`"Plural-Forms: nplurals=2; plural=(n != 1);\n"`).
--
Ticket URL: <https://code.djangoproject.com/ticket/30439#comment:49>
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.52d02dbcb1823282f9da5b990cc67d7a%40djangoproject.com.
