innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #14541 -- Corrected an outdated bit of wording in the LANGUAGES setting docs. Thanks to akelm for the report and suggested fix. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@14333 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Gabriel Hurley 2010-10-23 22:14:57 +00:00
parent d371142001
commit a200cc6d54
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/settings.txt
View File

@ -984,7 +984,7 @@ Generally, the default value should suffice. Only set this setting if you want
to restrict language selection to a subset of the Django-provided languages. to restrict language selection to a subset of the Django-provided languages.
If you define a custom ``LANGUAGES`` setting, it's OK to mark the languages as If you define a custom ``LANGUAGES`` setting, it's OK to mark the languages as
translation strings (as in the default value displayed above) -- but use a translation strings (as in the default value referred to above) -- but use a
"dummy" ``gettext()`` function, not the one in ``django.utils.translation``. "dummy" ``gettext()`` function, not the one in ``django.utils.translation``.
You should *never* import ``django.utils.translation`` from within your You should *never* import ``django.utils.translation`` from within your
settings file, because that module in itself depends on the settings, and that settings file, because that module in itself depends on the settings, and that