On May 20, 2005, at 2:25 PM, Neil Schemenauer wrote:
I don't think I agree with this change. set_content_type() worked like that for a reason. Usually when you call set_content_type() you are changing the content-type to something non-text (e.g. an image). In that case you want the charset to be iso-8859-1. You don't want the response to be encoded using DEFAULT_CHARSET. If you want some ofher charset then you really should provide it explicitly to the set_content_type() call.
What should be the result of this? response.set_charset('utf-8') response.set_content_type('text/rss+xml') The intent is clear, but the result is a surprise.
I think the charset parameter should either be required for all calls to set_content_type(), or else it should not be present. Doesn't changing the charset because "most" calls are for images seem a little speculative and a lttle magical? Besides, the DEFAULT_CHARSET *is* iso-8859-1, right?
_______________________________________________ Quixote-users mailing list [email protected] http://mail.mems-exchange.org/mailman/listinfo/quixote-users
