Added note to 'If you don't need internationalization' section of docs/i18n.txt about removing the i18n context processor

git-svn-id: http://code.djangoproject.com/svn/django/trunk@3608 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2006-08-18 03:43:55 +00:00
parent 53348672c9
commit e7a91d3e06
1 changed files with 3 additions and 2 deletions

View File

@ -48,9 +48,10 @@ bit of i18n-related overhead in certain places of the framework. If you don't
use internationalization, you should take the two seconds to set use internationalization, you should take the two seconds to set
``USE_I18N = False`` in your settings file. If ``USE_I18N`` is set to ``USE_I18N = False`` in your settings file. If ``USE_I18N`` is set to
``False``, then Django will make some optimizations so as not to load the ``False``, then Django will make some optimizations so as not to load the
internationalization machinery. internationalization machinery. See the `documentation for USE_I18N`_.
See the `documentation for USE_I18N`_. You'll probably also want to remove ``'django.core.context_processors.i18n'``
from your ``TEMPLATE_CONTEXT_PROCESSORS`` setting.
.. _documentation for USE_I18N: http://www.djangoproject.com/documentation/settings/#use-i18n .. _documentation for USE_I18N: http://www.djangoproject.com/documentation/settings/#use-i18n