#30439: Translations issues on Django upgrade due to unexpected changes in
plural
forms
--------------------------------------+------------------------------------
Reporter: Michal Čihař | Owner: Rodrigo
Type: Bug | Status: assigned
Component: Internationalization | Version: 2.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Michal Čihař):
If you don't care about translations coming from Django, you can use
workaround similar as we do in Weblate - on merge we replace the plural
formula. Django localization is typically loaded first and then your apps,
so that makes your app plural formula win. The code for this is here:
https://github.com/WeblateOrg/weblate/blob/36eaa21c55f8979e522e991759456b028f7c2912/weblate/utils/django_hacks.py
This is not a proper solution as it just makes it bad for Django
localization, but we use very little of those strings (if any), so it is
not a problem for Weblate.
--
Ticket URL: <https://code.djangoproject.com/ticket/30439#comment:30>
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.6b78621cbbdba2654bc122bbc793b35e%40djangoproject.com.
