Small edit to docs/i18n.txt from [6461]

git-svn-id: http://code.djangoproject.com/svn/django/trunk@6765 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2007-11-30 05:08:26 +00:00
parent efc1ff2004
commit 53a5fa9928
1 changed files with 2 additions and 2 deletions

View File

@ -461,8 +461,8 @@ otherwise, they'll be tacked together without whitespace!
you'll be using to edit the content. Due to the way the ``gettext`` tools you'll be using to edit the content. Due to the way the ``gettext`` tools
work internally and because we want to allow non-ASCII source strings in work internally and because we want to allow non-ASCII source strings in
Django's core and your applications, you **must** use UTF-8 as the encoding Django's core and your applications, you **must** use UTF-8 as the encoding
for your PO file (this means that everybody will be using the same for your PO file. This means that everybody will be using the same
encoding, which is important when Django processes the PO files). encoding, which is important when Django processes the PO files.
To reexamine all source code and templates for new translation strings and To reexamine all source code and templates for new translation strings and
update all message files for **all** languages, run this:: update all message files for **all** languages, run this::