Permalink
Browse files

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

git-svn-id: http://code.djangoproject.com/svn/django/trunk@6765 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent efc1ff2 commit 53a5fa9928a2134fe5fa4855aeddecbd71c10d23 @adrianholovaty adrianholovaty committed Nov 30, 2007
Showing with 2 additions and 2 deletions.
  1. +2 −2 docs/i18n.txt
View
@@ -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
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
- for your PO file (this means that everybody will be using the same
- encoding, which is important when Django processes the PO files).
+ for your PO file. This means that everybody will be using the same
+ encoding, which is important when Django processes the PO files.
To reexamine all source code and templates for new translation strings and
update all message files for **all** languages, run this::

0 comments on commit 53a5fa9

Please sign in to comment.