i18n should ideally respect the languages supported on a per-application basis
|Reported by:||Esaj||Owned by:||hugo|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
What if my main site application is only available in
'en' translations, but the user's Accept-Language header is set to
'de' (in that order)? Instead of using 'de' it will fall back to 'en'. This is because
'ru' is listed in LANGUAGES, so it sets the user language to
'ru'. However, there are no translation strings for
'ru' for the main site application, so it falls back to
There needs to be some respect for which languages each application has support for, to solve this i.e. the set of supported languages should be considered per application. This is more of an enhancement request than a defect, since I can always change LANGUAGES to be what I want, e.g.
('de', 'en') in the above example.
Change History (12)
comment:2 Changed 11 years ago by
|Owner:||changed from Adrian Holovaty to anonymous|
|Status:||new → assigned|