Changes between Version 2 and Version 4 of Ticket #28636


Ignore:
Timestamp:
Sep 28, 2017, 4:01:24 AM (7 years ago)
Author:
Denis Anuschewski
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #28636

    • Property Needs documentation set
  • Ticket #28636 – Description

    v2 v4  
    1 **Problem**: In the current state, the user's discovered language preference is only returned when found in `settings.LANGUAGES`. That's more than sufficient for the normal translation routine, but there seems to be no way (at least no DRY way) to find out a user's preference REGARDLESS of `settings.LANGUAGES`.
     1**Problem**: The user's discovered language preference is only returned when found in `settings.LANGUAGES`. That's more than sufficient for the normal translation routine, but there seems to be no way (at least no DRY way) to find out a user's preference REGARDLESS of `settings.LANGUAGES`.
    22
    33**Suggestion**: It would be nice to have an easy way for finding out a languange preference from request, even if it's not listed in your supported languages. You could think of an optional flag, so that the preference from `get_language_from_request` is checked against `LANG_INFO` in the translation module rather than against `settings.LANGUAGES`. This would give you one of all available languages in the translation module. You could use that e.g. for comparing with `settings.LANGUAGE_CODE` and add a fallback for specific cases.
Back to Top