summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
authorMariusz Felisiak <felisiak.mariusz@gmail.com>2023-01-06 14:46:33 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2023-01-17 11:49:15 +0100
commit8d98f99a4ab5de6f2c730399f53eba8bf6bea470 (patch)
treec9c643c4c77b0d5fb014270f62ba2ca193befc8a /docs/topics
parent0be8095b254fad65b2480d677ebe6098c41bbad6 (diff)
Refs #32873 -- Removed settings.USE_L10N per deprecation timeline.
Diffstat (limited to 'docs/topics')
-rw-r--r--docs/topics/i18n/formatting.txt21
-rw-r--r--docs/topics/i18n/index.txt7
2 files changed, 7 insertions, 21 deletions
diff --git a/docs/topics/i18n/formatting.txt b/docs/topics/i18n/formatting.txt
index b83c31e936..d58a52de30 100644
--- a/docs/topics/i18n/formatting.txt
+++ b/docs/topics/i18n/formatting.txt
@@ -9,12 +9,8 @@ Django's formatting system is capable of displaying dates, times and numbers in
templates using the format specified for the current
:term:`locale <locale name>`. It also handles localized input in forms.
-When it's enabled, two users accessing the same content may see dates, times and
-numbers formatted in different ways, depending on the formats for their current
-locale.
-
-The formatting system is enabled by default. To disable it, it's
-necessary to set :setting:`USE_L10N = False <USE_L10N>` in your settings file.
+Two users accessing the same content may see dates, times and numbers formatted
+in different ways, depending on the formats for their current locale.
.. note::
@@ -55,9 +51,8 @@ argument::
Controlling localization in templates
=====================================
-When you have enabled formatting with :setting:`USE_L10N`, Django
-will try to use a locale specific format whenever it outputs a value
-in a template.
+Django tries to use a locale specific format whenever it outputs a value in a
+template.
However, it may not always be appropriate to use localized values --
for example, if you're outputting JavaScript or XML that is designed
@@ -80,9 +75,6 @@ Template tags
Enables or disables localization of template variables in the
contained block.
-This tag allows a more fine grained control of localization than
-:setting:`USE_L10N`.
-
To activate or deactivate localization for a template block, use::
{% load l10n %}
@@ -95,11 +87,6 @@ To activate or deactivate localization for a template block, use::
{{ value }}
{% endlocalize %}
-.. note::
-
- The value of :setting:`USE_L10N` isn't respected inside of a
- ``{% localize %}`` block.
-
See :tfilter:`localize` and :tfilter:`unlocalize` for template filters that will
do the same job on a per-variable basis.
diff --git a/docs/topics/i18n/index.txt b/docs/topics/i18n/index.txt
index 77086c7f0f..d7b8087640 100644
--- a/docs/topics/i18n/index.txt
+++ b/docs/topics/i18n/index.txt
@@ -54,10 +54,9 @@ More details can be found in the `W3C Web Internationalization FAQ`_, the `Wikip
.. warning::
- Translation and formatting are controlled by :setting:`USE_I18N` and
- :setting:`USE_L10N` settings respectively. However, both features involve
- internationalization and localization. The names of the settings are an
- unfortunate result of Django's history.
+ Translation is controlled by the :setting:`USE_I18N` setting. However, it
+ involves internationalization and localization. The name of the setting is
+ an unfortunate result of Django's history.
Here are some other terms that will help us to handle a common language: