httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 55741] Documentation is served with incorrect character encoding
Date Tue, 05 Nov 2013 15:43:33 GMT

--- Comment #7 from Leif Halvard Silli <> ---
(In reply to Dirkjan Ochtman from comment #6)
> (In reply to Nick Kew from comment #4)
> > In any case, it looks like a firefox issue (or a local issue).  I haven't
> > checked it in the latest update, but when I first worked on charset issues,
> > the HTTP spec *explicitly* made iso-9958-1 a default if no explicit
> > content-type was indicated.  Hence a browser needs, at a minimum, to accept
> > it.
> That may be so, but I think a bunch of this changed with HTML5 and new-found
> enthusiasm for standardizing actual browser behavior. Please check the W3C
> table I linked to in the description.

“A bunch“ is very unspecific. And HTTP is almost irrelevant to the issue.

As a HTML WG invited expert, pointing to the latest draft, I can say that most
Firefox locales default to WINDOWS-1252/ISO-8859-1:

So, if  your alpha version of Firefox 27 parses that page as UTF-8, then it
must be because something causes your browser to default to UTF-8. 

All this being said: If the page *had* declared the encoding properly, we would
not have been having this discussion. Because, as is, the page does *not*
declare any encoding in a HTML conforming way - HTML5 conformance, these days,
is regulated by HTML5.

When the browsers fails to find a encoding definition, HTML5.x instructs the
parser to default to some encoding - usually a locale default, but it could
also be a another default.

So, to Nick Kew: It is wrong to say that this is local issue. More correct is
that HTML5.x *requires* the browser to fallback to a local encoding when the
page - as is the the case here - fails to declare the encoding.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message