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. _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
