Changes between Version 4 and Version 5 of UnicodeBranch


Ignore:
Timestamp:
05/11/07 10:01:56 (8 years ago)
Author:
mtredinnick
Comment:

Updated current status.

Legend:

Unmodified
Added
Removed
Modified
  • UnicodeBranch

    v4 v5  
    3333 1. Template rendering ('''Done''' in [4971])
    3434 2. Database I/O ('''Done''' in [4971] for postgresql, postgresql_psycopg2, mysql, mysql_old and sqlite backends)
    35     * Needs testing for servers/tables that are not in UTF-8 or ASCII encoding. The theory is that the client connection for each backend ''should'' be automatically converting everything to UTF-8 or Unicode objects (depends on backend), but this needs verifying.
    36  3. Model class support
    37  4. Form input encoding
     35    * Needs testing for servers/tables that are not in UTF-8 or ASCII encoding. The theory is that the client connection for each backend ''should'' be automatically converting everything to UTF-8 or Unicode objects (depends on backend), but this needs verifying. ''(Ivan Sagalaev and Malcolm have tested this feature a fair bit with various database servers, but more stress tests would be nice.)''
     36 3. Model class support ('''Done''' in [5057])
     37 4. Form input encoding ('''Done''' in [5192])
    3838 5. Other output methods (if necessary; unchecked as yet)
    3939    * syndication
     
    4646 * Decide on usage of gettext() versus ugettext() in a number of places.
    4747 * Look at rewriting gettext_lazy() so that it acts as a better string and unicode proxy.
     48
     49Finally, some documentation needs to be written describing good practices for creating unicode-aware Django apps.
Back to Top