On Sat, Jan 29, 2005 at 01:53:58AM -0500, Neil Schemenauer wrote:
> We could add a DEFAULT_CHARSET attribute to HTTPResponse (see the
> attached patch).  There is still a problem with set_content_type(),
> I think.  set_content_type() is often used when serving up binary
> data.  In that case I don't think you want to default charset to be
> UTF-8, even though you probably want text/* responses to be UTF-8.

   You don't want to set a charset even on all text/* responses.
Browsers behave badly (and every browser behaves badly in its own way)
if you set a charset on text/css responses. I'd like to advice everyone
to never set a charset for text/css responses.

Oleg.
--
     Oleg Broytmann            http://phd.pp.ru/            phd@phd.pp.ru
           Programmers don't die, they just GOSUB without RETURN.