Wrong charsets picked up

[Stephan Kulow]

Am Wednesday 14 April 2004 02:51 schrieb Dirk Mueller:
> On Friday 09 April 2004 23:58, Thiago Macieira wrote:
> > Also for the last two cases, I've come up with a fix. It's attached to
> > bug #79065. I want to commit it if possible.
>
> That patch doesn't look correct to me. The web browser has to ignore the
> HTTP charset when the document specifies one. Your patch appears to break
> this.
I can't say what the patch does exactly, but you confused me with that
statement.

http://www.w3.org/TR/html4/charset.html says
> To sum up, conforming user agents must observe the following priorities when 
> determining a document's character encoding (from highest priority to 
> lowest): 
> * An HTTP "charset" parameter in a "Content-Type" field.
> * A META declaration with "http-equiv" set to "Content-Type" and a value 
>    set for "charset". 
> * The charset attribute set on an element that designates an external 
>    resource. 

So the document comes after the HTTP charset in my reading.

Greetings, Stephan