diff options
| author | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2007-03-12 10:52:21 +0000 |
|---|---|---|
| committer | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2007-03-12 10:52:21 +0000 |
| commit | adbd80ae7fcfef612a70a9e2b2c12b800530c9fc (patch) | |
| tree | a8705c681da8f1d059bdeb1dcc49662eacdcb5c3 /docs | |
| parent | e5fa609ba71583efeb25b7167c7e55708e3d8189 (diff) | |
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
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/i18n.txt | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/docs/i18n.txt b/docs/i18n.txt index 7c220c22af..d430a56160 100644 --- a/docs/i18n.txt +++ b/docs/i18n.txt @@ -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 ------------- |
