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. ____ FYI from December 1999, see the HTML 4.01 Specification, section 5.2.2 http://www.w3.org/TR/REC-html40/charset.html#h-5.2.2 | (from highest priority to lowest): | | 1. An HTTP "charset" parameter in a "Content-Type" field. | 2. A META declaration with "http-equiv" set to "Content-Type" and a value set for "charset". | 3. The charset attribute set on an element that designates an external resource. This year, June 2013, from Mozilla's website https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta | * This <meta> element is only a part of the algorithm to determine | the character set of a page that browsers apply. Especially, the | HTTP Content-Type header and any BOM elements have precedence over | this element. -- Kind regards Ralph _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
