#34297: ValueError: invalid token in plural form: EXPRESSION when adding new
language
-------------------------------------+-------------------------------------
Reporter: Azat | Owner: nobody
Type: Bug | Status: closed
Component: Utilities | Version: 4.1
Severity: Normal | Resolution: invalid
Keywords: gettext, i18n, l10n | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Barney Szabolcs):
I used to be able to add any unsupported language to Django (so and yue)
(and I even deployed to prod yesterday), now I can't even run
makemessages, and runserver does not start, with the exact same message.
Probably it is because gettext got updated on homebrew and it does
something differently.
I think we should still be able to add unsupported languages without any
hustle, like we used to do. (I just had to add the language to locale
directory and I didn't even have to change settings.py). I know, for a
proper bug I should be able to pin down the exact version numbers, but it
seems to be wrong since django 3, and I was just lucky to have been using
the right version of gettext.🤷🏻
--
Ticket URL: <https://code.djangoproject.com/ticket/34297#comment:4>
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/0107018ea61ad6f0-d16b29f3-a3b7-4aa8-a106-4771341133b0-000000%40eu-central-1.amazonses.com.
