Closed Bug 278326 Opened 18 years ago Closed 18 years ago
Server charset takes precedence over page charset
The given URL claims this in the http headers: Content-Type: text/html; charset=WINDOWS-1251 but in the page itself, it says: <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> The content of the page is clearly meant to be western, not russian, but mozilla autodetects it as WINDOWS-1251. Hence, it displays with a really awful font (will attach screenshot) because for some reason that font is the one mozilla is calling up for cyrillic (wish I could figure out what font it is and nuke it!) Specifying Western from View->Charsets fixes the font. I've been seeing this periodically for a long time, over a year, but only just now traced it to a charset problem. (Some of the pages where I see it are incorrectly claiming that charset, and that's their fault, not mozilla's, but in this particular case the page's meta tag is correct even though the server isn't.) It still happens in 1.8a6.
see my comment in bug 278325
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
(In reply to comment #0) > (will attach screenshot) because for some reason that font is the one mozilla is > calling up for cyrillic (wish I could figure out what font it is and nuke it!) It seems like you're using Gtk1+X11core font build. You'd get a lot better rendering if you download 'gtk2+xft' build (go to ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/releases) and download one with 'gtk2+xft' in its name.
You need to log in before you can comment on or make changes to this bug.