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

Fixed #3084 -- Fixed typo pointed out by Simon Greenhill. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@4709 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-03-12 10:52:21 +00:00
parent e5fa609ba7
commit adbd80ae7f
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/i18n.txt
View File

@ -284,13 +284,14 @@ obtain) the language translations themselves. Here's how that works.
.. admonition:: Locale restrictions
Django does support localising your application into a locale for which
Django itself has not been translated -- 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 are wanting to 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 core.
Django does not support localising your application into a locale for
which Django itself has not been translated -- 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 are wanting
to 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
core.
Message files
-------------