Philip Taylor <p.tay...@rhul.ac.uk> wrote: > > > Rob wrote: >> Philip Taylor <p.tay...@rhul.ac.uk> wrote: >>> >>> >>> Rob (<nom...@example.com>) 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
I think it is a ridiculous standard, and I was surprised because we have large sites that are still in iso-8859-1 and work correctly. So I investigated a bit, and found that the real problem is that the webserver that Ken uses now sends the character set in the Content-Type header. Probably it did not do that before, and everything worked Ok. It has long been customary for webservers to send: Content-Type: text/html for .html files, and when the document itself has a meta http-equiv with Content-Type and the desired character set, everything works fine even with the broken standard. But now, the server sends: Content-Type: text/html; charset=UTF8 and suddenly the html document cannot set the correct charset anymore! When the server has no way of determining the charset of the .html document, it should not act like this. But probably this was a change with different motives than compatability. It looks like Ken is forced to change al his documents to UTF8 because of this change by his hoster, unless he can do something like creating a .htaccess file in the root of his webpage with: AddType text/html html or: AddType 'text/html; charset=windows-1252' html When that is allowed by the hoster, it would fix it for now. _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
