test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Removed obsolete locale restriction admonition 

Refs #14461. Thanks Ramiro Morales for pointing this.
This commit is contained in:
Claude Paroz 2013-11-08 16:47:19 +01:00
parent f2e0266be7
commit b780d03d62
1 changed files with 0 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/topics/i18n/translation.txt
View File

@ -1215,21 +1215,6 @@ Once the string literals of an application have been tagged for later
translation, the translation themselves need to be written (or obtained). Here's translation, the translation themselves need to be written (or obtained). Here's
how that works. how that works.
.. _locale-restrictions:
.. admonition:: Locale restrictions
Django does not support localizing your application into a locale for which
Django itself has not been translated. In this case, it will ignore your
translation files. If you were to try this and Django supported it, you
would inevitably see a mixture of translated strings (from your application)
and English strings (from Django itself). If you want to support a locale
for your application that is not already part of Django, you'll need to make
at least a minimal translation of the Django core.
A good starting point is to copy the Django English ``.po`` file and to
translate at least some :term:`translation strings <translation string>`.
Message files Message files
------------- -------------
@ -1689,13 +1674,6 @@ Notes:
the *real* ``ugettext()`` in any code that uses :setting:`LANGUAGES` at the *real* ``ugettext()`` in any code that uses :setting:`LANGUAGES` at
runtime. runtime.
* The ``LocaleMiddleware`` can only select languages for which there is a
Django-provided base translation. If you want to provide translations
for your application that aren't already in the set of translations
in Django's source tree, you'll want to provide at least a basic
one as described in the :ref:`Locale restrictions<locale-restrictions>`
note.
Once ``LocaleMiddleware`` determines the user's preference, it makes this Once ``LocaleMiddleware`` determines the user's preference, it makes this
preference available as ``request.LANGUAGE_CODE`` for each preference available as ``request.LANGUAGE_CODE`` for each
:class:`~django.http.HttpRequest`. Feel free to read this value in your view :class:`~django.http.HttpRequest`. Feel free to read this value in your view