- From: Michael[tm] Smith <mike@w3.org>
- Date: Sat, 23 Mar 2013 07:09:13 +0900
- To: "Jukka K. Korpela" <jkorpela@cs.tut.fi>
- Cc: Christopher Head <chead@chead.ca>, www-validator@w3.org
"Jukka K. Korpela" <jkorpela@cs.tut.fi>, 2013-03-22 15:52 +0200: > 2013-03-21 23:03, Christopher Head wrote: > > >I verified a document with <meta charset="ISO-8859-1">. The validator > >reported that "Bad value ISO-8859-1 for attribute charset on element > >meta: iso-8859-1 is not a preferred encoding name. The preferred label > >for this encoding is windows-1252.". > > This is a bug in the W3C Validator. Actually, it's not. It's the result of an intentional update I pushed to the W3C validator a couple of days ago in order to bring it in line with the current HTML spec, which no longer references the IANA charset registry but instead now normatively references the Encoding standard: http://encoding.spec.whatwg.org/ In that spec, the proper (preferred) name of the encoding is "windows-1252", and "iso-8859-1" is a (non-preferred) label for that. > It does not exist at http://validator.nu on which the W3C Validator is > based. So this will probably be fixed in a few weeks or years. It does not exist in http://validator.nu yet but it will as soon as Henri pushes the change to it. It's already changed in the validator sources. ... > This is a misunderstanding. They are both preferred MIME names, for two > different encodings. The registry > http://www.iana.org/assignments/character-sets/character-sets.xml That registry is now irrelevant as far as document-conformance rules for HTML documents go. The Encoding standard is the authoritative source for encoding of HTML documents. --Mike -- Michael[tm] Smith http://people.w3.org/mike
Received on Friday, 22 March 2013 22:09:18 UTC