From 53a5fa9928a2134fe5fa4855aeddecbd71c10d23 Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Fri, 30 Nov 2007 05:08:26 +0000 Subject: [PATCH] Small edit to docs/i18n.txt from [6461] git-svn-id: http://code.djangoproject.com/svn/django/trunk@6765 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/i18n.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/i18n.txt b/docs/i18n.txt index 8beb2188e86..1ae30241571 100644 --- a/docs/i18n.txt +++ b/docs/i18n.txt @@ -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::