  
  .. versionadded:: 1.2
  
  If :setting:`USE_I18N` is set to ``True`` then the generated cache key will
  include the name of the active :term:`language<language code>`.
  This allows you to easily cache multilingual sites without having to create
  the cache key yourself.
  
  See :doc:`/topics/i18n/deployment` for more on how Django discovers the active
  language.
  
  __ `Controlling cache: Using other headers`_
  
  The per-view cache
  ==================
 
</s> remove A boolean that specifies if data will be localized by default or not. If this
is set to ``True``, e.g. Django will display numbers and dates using the
format of the current locale.
 </s> add A boolean that specifies if localized formatting of data will be enabled by
default or not. If this is set to ``True``, e.g. Django will display numbers and
dates using the format of the current locale. </s> remove :ref:`using-translations-in-your-own-projects`.
 </s> add :ref:`how-django-discovers-translations`. </s> remove A boolean that specifies whether Django's internationalization system should be
enabled. This provides an easy way to turn it off, for performance. If this is
set to ``False``, Django will make some optimizations so as not to load the
internationalization machinery.
 </s> add A boolean that specifies whether Django's translation system should be enabled.
This provides an easy way to turn it off, for performance. If this is set to
``False``, Django will make some optimizations so as not to load the
translation machinery. </s> remove Django has full support for internationalization of text in code and
templates, and format localization of dates and numbers. Here's how it works.
 </s> add The goal of internationalization and localization is to allow a single Web
application to offer its content in languages and formats tailored to the
audience.

Django has full support for :doc:`translation of text
</topics/i18n/translation>` and :doc:`formatting of dates, times and numbers
</topics/i18n/formatting>`. </s> remove :doc:`Internationalization documentation </topics/i18n/internationalization>`.
 </s> add :doc:`translation documentation </topics/i18n/translation>`.
include the name of the active :term:`language<language code>` -- see also
:ref:`how-django-discovers-language-preference`). This allows you to easily
cache multilingual sites without having to create the cache key yourself.
  
  .. versionadded:: 1.2
  
  If :setting:`USE_I18N` is set to ``True`` then the generated cache key will
include the name of the active :term:`language<language code>` -- see also
:ref:`how-django-discovers-language-preference`). This allows you to easily
cache multilingual sites without having to create the cache key yourself.
include the name of the active :term:`language<language code>` -- see also
:ref:`how-django-discovers-language-preference`). This allows you to easily
cache multilingual sites without having to create the cache key yourself.
include the name of the active :term:`language<language code>` -- see also
:ref:`how-django-discovers-language-preference`). This allows you to easily
cache multilingual sites without having to create the cache key yourself.
include the name of the active :term:`language<language code>` -- see also
:ref:`how-django-discovers-language-preference`). This allows you to easily
cache multilingual sites without having to create the cache key yourself.
include the name of the active :term:`language<language code>` -- see also
:ref:`how-django-discovers-language-preference`). This allows you to easily
cache multilingual sites without having to create the cache key yourself.
include the name of the active :term:`language<language code>` -- see also
:ref:`how-django-discovers-language-preference`). This allows you to easily
cache multilingual sites without having to create the cache key yourself.
  
  __ `Controlling cache: Using other headers`_
  
  The per-view cache
  ==================
keep keep keep keep replace replace replace replace replace replace keep keep keep keep keep
 Fixed #17087 -- Re-organized the i18n docs to reduce confusion between USE_I18N/USE_L10N and the concepts of internationalization/localisation. Re
moved some duplicate content.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@17026 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/topics/cache.txt