Jeroen Ruigrok van der Werven wrote:
Makes sense given the recent push for making the Django core UTF8.
No, recent push is to make Django core Unicode (arrays of 2-byte
normalized characters). Django now is in UTF-8 (Unicode encoded to be
passed as single-byte strings) and this is the exact problem: it's
harder to work with UTF-8 then with Unicode.
The
majority of the MUA's out there already know how to support UTF8 in
emails.
In fact for emails I'm not that sure. People often are forced to read
email through old-style web-based mail readers that don't have any
notion of unicode in general and utf-8 in particular, admins set them up
to work in some legacy 1-byte encoding. This is why there is a
preference setting in Igor's patch.
