Django

Code

Changeset 6461

Show
Ignore:
Timestamp:
10/07/07 11:35:22 (1 year ago)
Author:
mtredinnick
Message:

Fixed the note about charset encoding in PO files. It must be UTF-8 since [5708].

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • django/trunk/docs/i18n.txt

    r6349 r6461  
    457457.. admonition:: Mind your charset 
    458458 
    459     When creating a ``.po`` file with your favorite text editor, first edit 
     459    When creating a PO file with your favorite text editor, first edit 
    460460    the charset line (search for ``"CHARSET"``) and set it to the charset 
    461     you'll be using to edit the content. Generally, utf-8 should work for most 
    462     languages, but ``gettext`` should handle any charset you throw at it. 
     461    you'll be using to edit the content. Due to the way the ``gettext`` tools 
     462    work internally and because we want to allow non-ASCII source strings in 
     463    Django's core and your applications, you **must** use UTF-8 as the encoding 
     464    for your PO file (this means that everybody will be using the same 
     465    encoding, which is important when Django processes the PO files). 
    463466 
    464467To reexamine all source code and templates for new translation strings and