- From: Ville Skytta <ville@dev.w3.org>
- Date: Sat, 15 Jan 2005 16:18:41 +0000
- To: www-validator-cvs@w3.org
Update of /sources/public/validator/httpd/cgi-bin
In directory hutz:/tmp/cvs-serv16277/httpd/cgi-bin
Modified Files:
check
Log Message:
Rephrase the "no charset parameter" message so that I won't repeatedly think
that the validator mistook the Server header as the Content-Type.
Index: check
===================================================================
RCS file: /sources/public/validator/httpd/cgi-bin/check,v
retrieving revision 1.375
retrieving revision 1.376
diff -u -d -r1.375 -r1.376
--- check 15 Jan 2005 16:14:05 -0000 1.375
+++ check 15 Jan 2005 16:18:38 -0000 1.376
@@ -422,9 +422,9 @@
}
my $ct = &ent($File->{ContentType});
&add_warning($File, 'note', 'Note:', <<".EOF.");
- The HTTP Content-Type header $_source[0] ($_source[1]) did not contain
- a "charset" parameter, but the Content-Type was one of the XML text/*
- sub-types (<code>$ct</code>). The relevant specification
+ The HTTP Content-Type header (<code>$ct</code>) $_source[0] ($_source[1])
+ did not contain a "charset" parameter, but the Content-Type was one of
+ the XML text/* sub-types. The relevant specification
(<a href="http://www.ietf.org/rfc/rfc3023.txt">RFC 3023</a>)
specifies a strong default of "us-ascii" for
such documents so we will use this value regardless of any encoding you
Received on Saturday, 15 January 2005 16:18:41 UTC