Changes between Version 11 and Version 12 of FeatureGrouping

Timestamp:

Feb 19, 2007, 1:19:02 PM (19 years ago)

Author:

Gary Wilson <gary.wilson@…>

Comment:

Character encoding issues

FeatureGrouping

@@ -4 +4 @@
 
 Please note that there is already a grouping of VersionOneFeatures.
+
+== Character encoding issues ==
+
+Several tickets are mentioned in this mailing list thread:
+[http://groups.google.com/group/django-developers/browse_thread/thread/4b71be8257d42faf/ unicode issues in multiple tickets (#952, #1356, #3370) and thread about Euro sign in django-users]
+
+Tickets:
+ * #3370, #1356, #952, #3370
+
+=== Comments made by Michael in the above mailing list thread ===
+
+The problem that started the original thread in django-users was that
+the MySQLdb backend thought it was using latin-1 encoding for the
+connection and therefore could not encode '€', which is in iso-8859-15
+but not in iso-8859-1 aka iso-latin-1. Ticket #2896 seems to explain how
+this can happen.
+
+In my opinion, each of the three tickets in the subject should solve
+this issue, and none tries to cope with templates written in a different
+encoding than settings.DEFAULT_ENCODING.
+
+#952 allows to use a different encoding on the connection than
+settings.DEFAULT_CHARSET. It does it for all backends.
+
+#1365 sets connection.charset in the mysql backend to utf8. This makes
+the MySQLdb use utf8 encoding, but it's hackish and has been reported
+not to work in all environments.
+
+#3370 opens the mysql backend connection with charset='utf8', which
+seems a cleaner way to do the same as #1365. It also fixes the __repr__
+of models (not sure if this is the best way, but this can be added to
+any of the other patches)
+
+My bottom line is that #952 has a different scope than the other two
+tickets, and that #1365 should be closed as duplicate of #3370. #3370
+and #952 can co-exist.
 
 == Pagination ==