Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed the note about charset encoding in PO files. It must be UTF-8 s…

…ince [5708].

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit a0102fccfd65c4259077a7ad899c166d46a5a23a 1 parent d2952d4
Malcolm Tredinnick authored October 07, 2007

Showing 1 changed file with 6 additions and 3 deletions. Show diff stats Hide diff stats

  1. 9  docs/i18n.txt
9  docs/i18n.txt
@@ -456,10 +456,13 @@ otherwise, they'll be tacked together without whitespace!
456 456
457 457
 .. admonition:: Mind your charset
458 458
-    When creating a ``.po`` file with your favorite text editor, first edit
+    When creating a PO file with your favorite text editor, first edit
460 460
     the charset line (search for ``"CHARSET"``) and set it to the charset
-    you'll be using to edit the content. Generally, utf-8 should work for most
-    languages, but ``gettext`` should handle any charset you throw at it.
+    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).
463 466
464 467
 To reexamine all source code and templates for new translation strings and
465 468
 update all message files for **all** languages, run this::

0 notes on commit a0102fc

Please sign in to comment.
Something went wrong with that request. Please try again.