id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
750	i18n should ideally respect the languages supported on a per-application basis	Esaj	hugo	"What if my main site application is only available in {{{'de'}}} and {{{'en'}}} translations, but the user's Accept-Language header is set to {{{'ru'}}}, {{{'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 {{{'en'}}}.

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."	defect	closed	Tools	0.90	minor	fixed			Unreviewed	0	0	0	0	0	0