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

Fixed #3084 -- Documented that Django's core must be translated into a 

particular locale for application translations in that locale to work.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@4707 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-03-12 09:02:18 +00:00
parent 173c76d038
commit 2a488f3cd4
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/i18n.txt
View File

@ -282,6 +282,16 @@ How to create language files
Once you've tagged your strings for later translation, you need to write (or Once you've tagged your strings for later translation, you need to write (or
obtain) the language translations themselves. Here's how that works. 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.
Message files Message files
------------- -------------