From fd06488fe36acc27fbe37bf7c9aefc0574e9cc4e Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 28 Jun 2018 10:25:46 -0400 Subject: Fixed links for i18n context processor docs. --- docs/topics/i18n/translation.txt | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) (limited to 'docs/topics') diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt index 2fe1497cf1..34313034c8 100644 --- a/docs/topics/i18n/translation.txt +++ b/docs/topics/i18n/translation.txt @@ -845,7 +845,7 @@ If you want to select a language within a template, you can use the While the first occurrence of "Welcome to our page" uses the current language, the second will always be in English. -.. _template-translation-vars: +.. _i18n-template-tags: Other tags ---------- @@ -880,8 +880,13 @@ locale's direction. If ``True``, it's a right-to-left language, e.g. Hebrew, Arabic. If ``False`` it's a left-to-right language, e.g. English, French, German, etc. -If you enable the ``django.template.context_processors.i18n`` context processor -then each ``RequestContext`` will have access to ``LANGUAGES``, +.. _template-translation-vars: + +``i18n`` context processor +~~~~~~~~~~~~~~~~~~~~~~~~~~ + +If you enable the :class:`django.template.context_processors.i18n` context +processor, then each ``RequestContext`` will have access to ``LANGUAGES``, ``LANGUAGE_CODE``, and ``LANGUAGE_BIDI`` as defined above. .. templatetag:: get_language_info -- cgit v1.3