Changes between Version 8 and Version 9 of UnicodeInDjango


Ignore:
Timestamp:
06/28/2006 11:37:15 AM (9 years ago)
Author:
Andrey
Comment:

commented about templates

Legend:

Unmodified
Added
Removed
Modified
  • UnicodeInDjango

    v8 v9  
    1111 * Special casing: what happens with GET parameters? those don't provide charsets, what should we do if DEFAULT_ENCODING is utf-8, but the GET parameters aren't valid utf-8? The clean way would be to throw an exception (like with all other places, too)
    1212   * The current URI spec ([http://www.ietf.org/rfc/rfc3986.txt RFC 3986]) clearly states that all URIs must be encoded according to UTF-8 so we can assume that this is the case. If this causes a !UnicodeDecodeError it makes sense to fall back on windows-1252 or latin-1. Has anyone taken a look at Mark Pilgrim's [http://chardet.feedparser.org/ Universal Encoding Detector]? - Noah Slater
     13 * template loaders need to do DEFAULT_CHARSET to unicode translation
    1314 * internal usage of str() needs to be checked and supposedly changed over to unicode() usage
    1415 * 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)
Back to Top