Browse files

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: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 173c76d commit 2a488f3cd412ad899ce32f3603cbc02db8f6c187 @malcolmt malcolmt committed Mar 12, 2007
Showing with 10 additions and 0 deletions.
  1. +10 −0 docs/i18n.txt
@@ -282,6 +282,16 @@ How to create language files
Once you've tagged your strings for later translation, you need to write (or
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

0 comments on commit 2a488f3

Please sign in to comment.