#28636: Allow customizing the fallback language from the locale middleware
-------------------------------------+-------------------------------------
Reporter: Denis Anuschewski | Owner: nobody
Type: New feature | Status: new
Component: | Version: master
Internationalization |
Severity: Normal | Resolution:
Keywords: translation, | Triage Stage: Accepted
internationalization, request |
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Denis Anuschewski):
Yes, I'm sure. Because what you implemented as a fallback differs from
what `add_fallback` is providing:
Your fallback determines what translation language to use when none is
found. `add_fallback` on the other hand gives a fallback on string basis
when no translation for the string ist found in a translation file.
So with your code a Spanish user e.g. get's Spanish language, but missing
Spanish translations get displayed in German. The Goal ist to have an
English fallback in this case which `add_fallback` provides.
--
Ticket URL: <https://code.djangoproject.com/ticket/28636#comment:17>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.43637716cb36e66f1aa781d98f6279fa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
