Rob wrote:
> Philip Taylor <[email protected]> wrote:
>>
>>
>> Rob (<[email protected]>) wrote:
>>
>>>>> Content-Type: text/html; charset=UTF-8
>>
>>>>> <meta http-equiv="Content-Type" content="text/html;
>>>>> charset=windows-1252">
>>
>>>> Nothing has changed. The HTTP Content-Type header has aways taken
>>>> precedence
>>>> over the HTML meta declaration, and not only in SM.
>>>
>>> Then why is the page shown in UTF-8 while it should be windows-1252?
>>
>> It should /not/ be Windows-1252. The W3C state that the http
>> content-type trumps the meta content-type [1], so the document should
>> be rendered in UTF-8.
>
> That is wrong, isn't it?
> This meta http-equiv has the specific purpose of setting the content
> type in cases where the http headers from the server are wrong and
> cannot be easily corrected.
Logically, I would say you are correct. But the W3C is the sole arbiter
of what is right and what is wrong w.r.t. the web, so if the W3C state
that the http content-type trumps the meta content-type, that behaviour
is correct. However, this has nothing to do with Seamonkey per se, so
it might be better to pursue it on an official W3C list such as
http://lists.w3.org/Archives/Public/www-html/
where you have real experts such as Juuka Korpela who will be able to
advise.
Philip Taylor
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
