Ralph Fox <[email protected]> wrote: > On Thu, 29 Aug 2013 02:37:27 -0500, Rob wrote: > >> The HTTP headers say UTF-8: >> >> HTTP/1.1 200 OK >> Date: Thu, 29 Aug 2013 07:31:25 GMT >> Server: Apache >> Last-Modified: Thu, 29 Aug 2013 04:44:38 GMT >> ETag: "e74073-a7a-c36f5980" >> Accept-Ranges: bytes >> Content-Length: 2682 >> Connection: close >> Content-Type: text/html; charset=UTF-8 >> >> <!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en"> >> <html><head> >> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> >> <meta name="Author" content="Ken Fletcher"> >> <meta name="GENERATOR" content="Mozilla/4.74 [en] (Win98; U) [Netscape]"> >> <title>Test Insert Symbols</title> >> <meta content="Seamonkey 2.20 Composer - Insert - Characters & Symbols >> 27 August 2013" name="description"> >> </head> >> >> The meta header should override it. Maybe that has been broken somehow? > > > 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? On my Linux system running Seamonkey 2.20 it fails as well. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
