From 6a25843fb15ef6bc9a2cf4e71925088712b5ac24 Mon Sep 17 00:00:00 2001 From: Georg Bauer Date: Wed, 19 Oct 2005 14:53:07 +0000 Subject: [PATCH] i18n: added a note on DjangoContext vs. Context with regard to LANGUAGES and LANGUAGE_CODE git-svn-id: http://code.djangoproject.com/svn/django/branches/i18n@955 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/translation.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/translation.txt b/docs/translation.txt index 2adb1a2283..c727cc3ad0 100644 --- a/docs/translation.txt +++ b/docs/translation.txt @@ -165,7 +165,11 @@ look like this:: This would jump to the same page you came from and pass the django_language variable. This is used in discovery of languages, as described in the next -chapter. +chapter. Of course this can only work if your rendering context contains +the LANGUAGE_CODE and LANGUAGES variables. If you use DjangoContext as +your rendering context, they are automatically defined. If you use the +simpler Context class, you need to pass them along from request.LANGUAGE_CODE +and settings.LANGUAGES themselve. How the Language is Discovered ==============================