On Fri, Nov 8, 2013 at 12:50 PM, Claude Paroz <[email protected]> wrote: > > Already committed: > https://github.com/django/django/commit/b780d03d624e712d7b1f6b6796058b950e975675
I've tried to also add tests for this: https://github.com/django/django/pull/1903 What I've found so far and what the tests show is (trying to use a translation contained in a path present in LOCALE_PATHS but not shipped with Django): * Translation after explicit call of traslation.activate(): Works without having to list the language in the LANGUAGES setting. * Translation when LocaleMiddleware detected the user preferred language from a language-code-prefixed URL: Works but only it the language is listed in the LANGUAGES setting. * Translation when LocaleMiddleware detected the user preferred language from the Accept-Language request header: Doesn't work. This means the TranslationNotInDjangoUrls.test_locale_paths_translation_ua_lang_pref() test fails. Opinions about if/why the current behavior is correct/consistent aer welcome. Or corrections to the tests if you can spot any problem with them. Regards, -- Ramiro Morales @ramiromorales -- You received this message because you are subscribed to the Google Groups "Django internationalization and localization" 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]. Visit this group at http://groups.google.com/group/django-i18n. For more options, visit https://groups.google.com/groups/opt_out.
