Context Navigation

Changes between Version 9 and Version 10 of UnicodeInDjango

v9	v10
9	9	* the HTTPResponse sending machinery needs to do the unicode to DEFAULT_CHARSET translation
10	10	* the HTTPRequest creation process needs to turn outside strings into unicode strings, using the provided charset (if given) or defaulting to DEFAULT_CHARSET (as that is what was sent to the browser when the form was transmitted)
	11	* 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.
11	12	* 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)
12	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