#35352: Unable to continue using custom languages with Django
-------------------------------------+-------------------------------------
               Reporter:  Barney     |          Owner:  nobody
  Szabolcs                           |
                   Type:  Bug        |         Status:  new
              Component:             |        Version:  4.2
  Internationalization               |
               Severity:  Release    |       Keywords:  custom languages
  blocker                            |
           Triage Stage:             |      Has patch:  0
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  1
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 with gettext version  0.22.5, Somali (so) and Cantonese (yue) stopped
 working.
 If I remove language files for these two languages, the runserver works
 fine,
 if I add back these two languages, error:  ValueError: invalid token in
 plural form: EXPRESSION

 Also, makemessages CommandError: Type 'manage.py help makemessages' for
 usage information.

 Whereas, if I run makemessages -l so -l yue it works fine, but still the
 project does not start, yielding the same error.

 This is a weird regression.

 Quick fix: if needed, I can generate a quick translation for the Django
 .po files, using ChatGPT, but I don't know anyone who speaks Somali or
 Cantonese.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35352>
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/0107018ea621ccf0-35ca2f72-72ac-4ba9-915a-79528ab534be-000000%40eu-central-1.amazonses.com.

Reply via email to