Changes between Version 11 and Version 12 of UnicodeInDjango


Ignore:
Timestamp:
Jun 7, 2012, 5:29:52 AM (12 years ago)
Author:
anonymous
Comment:

replace a dead link

Legend:

Unmodified
Added
Removed
Modified

  • UnicodeInDjango

    v11 v12  
    1111  * There should be a way to access the original "raw" (as bytes) GET and POST data. Django already provides raw POST data using the [http://www.djangoproject.com/documentation/request_response/#attributes  raw_post_data] attribute. Perhaps raw_get_data should also be added.
    1212 * 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)
    13    * 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   * 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://puzzlet.github.com/chardet/docs/index.html Universal Encoding Detector]? - Noah Slater
    1414 * template loaders need to do DEFAULT_CHARSET to unicode translation
    1515 * internal usage of str() needs to be checked and supposedly changed over to unicode() usage
Back to Top