On 8/30/13 11:34 AM +0900, Geoff Welsh wrote:
Geoff Welsh wrote:
Philip Taylor 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.
Philip Taylor
--------
[1]
http://www.w3.org/International/questions/qa-html-encoding-declarations)
:
The HTTP header information has the highest priority when it conflicts
with in-document declarations.
if I'm understanding this all correctly, the HTTP Header comes from the
server. And it overrides whatever the typical home (ISP based) author
puts in the page.
I've never run into this stuff before.
GW
I think I might try using " © " in the HTML source, rather than the
symbol
GW
Or just change the encoding on the site's pages and upload them to the
server. Since the server wants UTF-8, give it UTF-8. Problem solved.
--
/////////////////////////////////////////////////////////
// Trane Francks [email protected] Tokyo, Japan
// Practice random kindness and senseless acts of beauty.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
