Changes between Version 4 and Version 5 of UnicodeInDjango


Ignore:
Timestamp:
01/10/2006 04:34:19 PM (10 years ago)
Author:
verbosus
Comment:

added the unicode normalization issue

Legend:

Unmodified
Added
Removed
Modified
  • UnicodeInDjango

    v4 v5  
    1313 * debugging stuff needs to use repr() on strings, not str() (or use unicode() and let the HTTP response handling stuff handle the conversion - most debugging stuff is working with the response machinery anyway)
    1414 * mail sending functions need to do the right thing with the MIME type
     15 * we should decide wether to normalize the input unicode data so that at the database or application level we can match strings regardless of their decomposition (see the standard lib’s [http://docs.python.org/lib/module-unicodedata.html unicodedata module ] with its `normalize()` function). I would go for NFC, if there’s consensus around normalizing.
    1516
    1617Please either complete the above list or add headlines with more detailed discussions of the points above. Please only post results here, discussion should take place on the django-developer list.
Back to Top