#28636: Translation module: Check `LANG_INFO` against user's language
preference as
optional feature
-------------------------------------+-------------------------------------
Reporter: Denis Anuschewski | Owner: nobody
Type: New feature | Status: new
Component: | Version: 1.11
Internationalization |
Severity: Normal | Resolution:
Keywords: translation, | Triage Stage:
internationalization, request | Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
Yes, I understand the difference of output produced by your code. However,
I would like to completely understand your use case to be sure we are
fixing it at the right level.
Returning to your example, why would you like to get a language code which
is not in your site `LANGUAGES`? Why would the fallback language be
different depending on the requested language?
Maybe you could present a table whose columns are: language of original
strings, client language, LANGUAGE_CODE, LANGUAGES, resulting
language/fallback (one line with current code, one line with your wanted
situation).
--
Ticket URL: <https://code.djangoproject.com/ticket/28636#comment:10>
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.0cc28f3e1f830e8af618f2a8fea5af2f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
