On Sat, Nov 23, 2019 at 9:17 AM אורי <u...@speedy.net> wrote:
> By the way, I read here that this bug it the fault of Transifex (not > Django). I'm not sure what that means, it worked in Django 2.1. Someone > made a decision to change something in Django 2.2, how can it be Transifex? > It must be a decision of the Django developers. If Transifex has bugs, why > not use a previous version which worked? As far as I would suggest, I would > postpone using the 4-strings translation (or up to 6 strings in some > languages) to Django 5.0 or 10.0. Is it really that important to break all > the 2-strings translations which worked? > As far as I understand, the issue is the translations that are pulled in from Transifex (it's not a version of Transifex that we can control). I would hazard a guess that the same issue would occur with Django 2.1 if the translations were updated; i.e., it's simply a matter of timing that it happened to break with Django 2.2. There is some sample code in the ticket which might be good to try, to see if it fixes the issue for you: https://code.djangoproject.com/ticket/30439#comment:7 Cheers, *Tobias McNulty*Chief Executive Officer tob...@caktusgroup.com www.caktusgroup.com -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMGFDKTM_uhYYC7R7oaADfK%3D_4kaMNjH5U8FQ1q%3DYVdutzpwEg%40mail.gmail.com.
