Tightened docs/i18n.txt change from [4707]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@4748 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
515337fa3b
commit
cecd520671
|
@ -284,13 +284,13 @@ obtain) the language translations themselves. Here's how that works.
|
||||||
|
|
||||||
.. admonition:: Locale restrictions
|
.. admonition:: Locale restrictions
|
||||||
|
|
||||||
Django does not support localising your application into a locale for
|
Django does not support localizing your application into a locale for
|
||||||
which Django itself has not been translated -- it will ignore your
|
which Django itself has not been translated. In this case, it will ignore
|
||||||
translation files. If you were to try this and Django supported it, you
|
your translation files. If you were to try this and Django supported it,
|
||||||
would inevitably see a mixture of translated strings (from your
|
you would inevitably see a mixture of translated strings (from your
|
||||||
application) and English strings (from Django itself). If you are wanting
|
application) and English strings (from Django itself). If you want to
|
||||||
to support a locale for your application that is not already part of
|
support a locale for your application that is not already part of
|
||||||
Django, you will need to make at least a minimal translation of the Django
|
Django, you'll need to make at least a minimal translation of the Django
|
||||||
core.
|
core.
|
||||||
|
|
||||||
Message files
|
Message files
|
||||||
|
|
Loading…
Reference in New Issue