On Thursday, August 29, 2013 9:34:26 PM UTC-5, Geoff Welsh wrote: > Geoff Welsh wrote: > > > Philip Taylor wrote: > > >> > > >> > > >> Rob (<.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. > > >> > > >> 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
Geoff Welsh -- Thanks. I will experiment with that. Doing the actual html codes could be a good basic quick fix for me to do for restoring copyright symbols, and other isolated symbols on webpages. It may be more difficult for the much older story webpages from 10 years ago, where the left-quotes and right-quotes and apostrophes are also now displaying as <?>. Ken F _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
