W3C home > Mailing lists > Public > www-validator@w3.org > March 2016

Re: Charset recognition

From: Michael[tm] Smith <mike@w3.org>
Date: Thu, 10 Mar 2016 06:36:59 +0900
To: "Jukka K. Korpela" <jkorpela@cs.tut.fi>, Jukka Peltomäki <jukka.h.peltomaki@gmail.com>, www-validator@w3.org
Message-ID: <20160309213659.GC31414@sideshowbarker.net>
"Jukka K. Korpela" <jkorpela@cs.tut.fi>, 2016-03-09 11:50 +0200:
> Archived-At: <http://www.w3.org/mid/56DFF1F5.9020207@cs.tut.fi>
> 
> 9.3.2016, 11:31, Jukka Peltomäki wrote:
> 
> >The validator test result states "The Content-Type was text/html with no
> >charset specified. Used the HTML parser.", despite the fact that the
> >charset is specified with <meta charset="UTF-8"> in HTML5.
> 
> This seems to happen when the Content-Type HTTP response header, as sent by
> the server, specifies text/html without a charset parameter.

yes

> The validator still honors a <meta charset="..."> element if present.
> 
> So the informative message would be clearer with an addition and a change :
> “The Content-Type, as specified in HTTP headers, was text/html without a
> charset parameter.”

I’ve changed it so for this case it now says:

  The Content-Type header specified text/html but no charset. Used the HTML parser.

-- 
Michael[tm] Smith https://people.w3.org/mike

Received on Wednesday, 9 March 2016 21:37:24 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 March 2016 21:37:28 UTC