Changes between Version 4 and Version 5 of UnicodeBranch

Timestamp:

May 11, 2007, 10:01:56 AM (18 years ago)

Author:

Malcolm Tredinnick

Comment:

Updated current status.

UnicodeBranch

@@ -33 +33 @@
  1. Template rendering ('''Done''' in [4971])
  2. Database I/O ('''Done''' in [4971] for postgresql, postgresql_psycopg2, mysql, mysql_old and sqlite backends)
-    * 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.
- 3. Model class support
- 4. Form input encoding
+    * 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.)''
+ 3. Model class support ('''Done''' in [5057])
+ 4. Form input encoding ('''Done''' in [5192])
  5. Other output methods (if necessary; unchecked as yet)
     * syndication
@@ -46 +46 @@
  * Decide on usage of gettext() versus ugettext() in a number of places.
  * Look at rewriting gettext_lazy() so that it acts as a better string and unicode proxy.
+
+Finally, some documentation needs to be written describing good practices for creating unicode-aware Django apps.