Validator has become case-sensitive to the MEAT tag param CHARSET

The validator has evidently become case-sensitive to the parameter tag
"CHARSET" in the <META> content label sometime in the last few months.
Pages with tags like the following:

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=iso-8859-1">

that formerly validated with automatic detection of encoding now fail.
The only way to get them to validate (other than provisionally with a
set encoding) is to change the above to:

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">

I have seen several messages go through on this topic, and it appears
that the "CHARSET=" tag is not supposed to be case-sensitive. It is
particularly odd because I can change the case of the other tag values
and everything is fine:

<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="TEXT/HTML charset=ISO-8859-1">

validates with no problem; only the term "charset" is case-sensitive!
Is this going to be fixed, or do I have to change all my META tags to
get their pages to validate? Thanks,

	-rick bogart

Received on Thursday, 20 September 2007 14:26:50 UTC