From 3ac0e43207b4a1b9327ba12612005c285fbff7ee Mon Sep 17 00:00:00 2001 From: lufafajoshua <77637648+lufafajoshua@users.noreply.github.com> Date: Mon, 24 Jun 2024 12:02:55 +0200 Subject: Fixed #35306 -- Documented fallback localization formats in templates when localization is disabled. --- docs/ref/settings.txt | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt index 88ccf6106e..34c835fb82 100644 --- a/docs/ref/settings.txt +++ b/docs/ref/settings.txt @@ -1842,9 +1842,7 @@ standard :term:`language ID format `. For example, U.S. English is ``"en-us"``. See also the `list of language identifiers`_ and :doc:`/topics/i18n/index`. -:setting:`USE_I18N` must be active for this setting to have any effect. - -It serves two purposes: +It serves three purposes: * If the locale middleware isn't in use, it decides which translation is served to all users. @@ -1852,6 +1850,11 @@ It serves two purposes: user's preferred language can't be determined or is not supported by the website. It also provides the fallback translation when a translation for a given literal doesn't exist for the user's preferred language. +* If localization is explicitly disabled via the :tfilter:`unlocalize` filter + or the :ttag:`{% localize off %}` tag, it provides fallback + localization formats which will be applied instead. See + :ref:`controlling localization in templates ` for + details. See :ref:`how-django-discovers-language-preference` for more details. -- cgit v1.3