Changes between Version 4 and Version 5 of StringEncoding

Timestamp:

Apr 6, 2007, 5:25:27 AM (18 years ago)

Author:

Malcolm Tredinnick

Comment:

Fix formatting problem.

StringEncoding

@@ -103 +103 @@
 
  * Django does not currently handle arbitrary database encodings, unattached to the concept of DEFAULT_CHARSET.
-    + Add DEFAULT_CHARSET setting
-    + teach database backends how to encode unicode and bytestrings for the database (avoid pointless round-trips for bytestrings, if the target is UTF-8).
+    * Add DEFAULT_CHARSET setting
+    * teach database backends how to encode unicode and bytestrings for the database (avoid pointless round-trips for bytestrings, if the target is UTF-8).
  * The getttext() functions return bytestrings using DEFAULT_CHARSET. This causes a number of difficulties in the code, because UTF-8 encoded bytestrings cannot safely be passed to the string.join() method.
-    + Consider switching to ugettext() and friends everywhere internally. These return unicode strings that can be used in join() calls. The alternative requires being aware of when bytestrings might be involved and doing yet another decode()/encode() round-trip around the join(). Error-prone and time-consuming.
+    * Consider switching to ugettext() and friends everywhere internally. These return unicode strings that can be used in join() calls. The alternative requires being aware of when bytestrings might be involved and doing yet another decode()/encode() round-trip around the join(). Error-prone and time-consuming.