summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdrian Holovaty <adrian@holovaty.com>2007-03-16 15:23:28 +0000
committerAdrian Holovaty <adrian@holovaty.com>2007-03-16 15:23:28 +0000
commitcecd520671eb37785847c4573cade2a98c93c661 (patch)
tree6ad47c39d74d6f5601e5ca8a84b401455d5ccc4f
parent515337fa3b7279cfca3f4ce39a738efb6aab7586 (diff)
Tightened docs/i18n.txt change from [4707]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@4748 bcc190cf-cafb-0310-a4f2-bffc1f526a37
-rw-r--r--docs/i18n.txt14
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/i18n.txt b/docs/i18n.txt
index d430a56160..4a05e53ddf 100644
--- a/docs/i18n.txt
+++ b/docs/i18n.txt
@@ -284,13 +284,13 @@ obtain) the language translations themselves. Here's how that works.
.. admonition:: Locale restrictions
- 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
+ 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.
Message files