Changes between Version 109 and Version 110 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Jul 15, 2007, 5:19:07 AM (17 years ago)
Author:
Malcolm Tredinnick
Comment:

Added PO file encoding requirement.

Legend:

Unmodified
Added
Removed
Modified

  • BackwardsIncompatibleChanges

    v109 v110  
    2929 * [5609] July 4, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Unicodemerge Unicode merge]
    3030 * [5654] July 12, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Changed__init__parametersinsyndicationframeworksFeedclass Changed __init__() parameters in syndication framework's Feed class]
     31 * [5708] July 15, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#PofilesmustbeUTF-8encoded PO files must be UTF-8 encoded]
    3132
    3233== Database constraint names changed ==
    … …  
    241242
    242243This only affects people who have subclassed {{{Feed}}} and overridden the {{{__init__()}}} method, and people who have called {{{Feed.__init__()}}} directly from their own code. {{{Feed.__init__()}}} had not been documented.
     244
     245== PO files must be UTF-8 encoded ==
     246
     247In [5708] we added the ability to use non-ASCII strings as input to the translation framework. This was a frequently requested feature by developers whose original strings were not in English. A consequence of this change is that we have to specify the encoding of the PO files (the files used by translators to create translations). Following common practice in other projects, we have chosen UTF-8 as the encoding.
     248
     249This change only affects third-party developers who are using Django's make-messages.py script to extract their strings for their own PO files. The PO files will need to be saved and edited as UTF-8 files and the ''charset'' set correctly in the header of the file. All of Django's core translation files already satisfy this requirement.
Back to Top