Changes between Version 1 and Version 2 of UnicodeBranch


Ignore:
Timestamp:
Apr 7, 2007, 12:40:55 AM (18 years ago)
Author:
Malcolm Tredinnick
Comment:

Filled in basic content

Legend:

Unmodified
Added
Removed
Modified

  • UnicodeBranch

    v1 v2  
    1616The main goals of this branch are:
    1717
    18  * To be defined.
     18 * Make it easier for developers to work with non-ASCII character data when working with Django.
     19 * Be more consistent in our string handling behaviour inside Django (see StringEncoding for details on this).
    1920
    2021== Status ==
    2122
    2223The branch was created on April 7, 2007.
     24
     25== Todo Items ==
     26
     27The various pieces will be converted in roughly the following order:
     28
     29 1. Template rendering
     30 2. Database I/O (requires introducing new DATABASE_CHARSET setting)
     31 3. Model class support
     32 4. Form input encoding
     33 5. Other output methods (if necessary; unchecked as yet)
     34    * syndication
     35    * serialisation
     36    * Google sitemaps
     37 6. Other contrib modules
     38
     39We also need to look at the i18n support functions (in django.utils.translation):
     40
     41 * Decide on usage of gettext() versus ugettext() in a number of places.
     42 * Look at rewriting gettext_lazy() so that it acts as a better string and unicode proxy.
Back to Top