summaryrefslogtreecommitdiffstats
path: root/htdocs/docs/errors.html
diff options
context:
space:
mode:
authorlink <link@localhost>2001-07-24 10:18:31 +0000
committerlink <link@localhost>2001-07-24 10:18:31 +0000
commit0633d9ee3d5791eb6e7dc69638093ab645acb3e7 (patch)
tree67ec48b35e62ca20140ec663c3ac8e644c58c038 /htdocs/docs/errors.html
parent0c6e3ee02739cc103406104c2f4d1745cb8249dc (diff)
downloadmarkup-validator-0633d9ee3d5791eb6e7dc69638093ab645acb3e7.zip
markup-validator-0633d9ee3d5791eb6e7dc69638093ab645acb3e7.tar.gz
markup-validator-0633d9ee3d5791eb6e7dc69638093ab645acb3e7.tar.bz2
Don't report as Valid if DOCTYPE or Character Encoding was overridden.
Fix bug in UTF-8 BOM supression when DOCTYPE Override was in force. Add explanation for UTF-8 BOM "Supressed" message.
Diffstat (limited to 'htdocs/docs/errors.html')
-rwxr-xr-xhtdocs/docs/errors.html20
1 files changed, 17 insertions, 3 deletions
diff --git a/htdocs/docs/errors.html b/htdocs/docs/errors.html
index 1f1869c..613a4fd 100755
--- a/htdocs/docs/errors.html
+++ b/htdocs/docs/errors.html
@@ -8,8 +8,8 @@
<link rel="stylesheet" type="text/css" href="/base.css" />
<meta name="keywords" content="HTML, Hypertext Markup Language, Validation, W3C HTML Validation Service" />
<meta name="description" content="W3C's easy-to-use HTML validation service, based on an SGML parser." />
- <meta name="revision" content="$Id: errors.html,v 1.7 2001-07-14 22:19:59 link Exp $" />
- <meta name="modified" content="$Date: 2001-07-14 22:19:59 $" />
+ <meta name="revision" content="$Id: errors.html,v 1.8 2001-07-24 10:18:31 link Exp $" />
+ <meta name="modified" content="$Date: 2001-07-24 10:18:31 $" />
</head>
<body bgcolor="#FFFFFF" text="#000000" link="#0000ee" vlink="#551a8b">
@@ -559,6 +559,20 @@
the previous error referred to.
</p>
</dd>
+ <dt><a id="utf8-bom" name="utf8-bom">"UTF-8 'BOM' detected and removed"</a></dt>
+ <dd>
+ <p>
+ The document contained an UTF-8 encoded UNICODE Byte Order mark as
+ the first character and we have removed before parsing. The legality
+ of a UTF-8 encoded BOM in XML is controversial and many XML Processors
+ do not allow it. To be on the safe side you should avoid using the
+ BOM in UTF-8 encoded documents.
+ </p>
+ <p>
+ Note, though, that the BOM in <em>UTF-16</em> encoded documents
+ is non-controverial and handled by all conforming XML Processors.
+ </p>
+ </dd>
</dl>
<hr />
@@ -567,7 +581,7 @@
src="http://validator.w3.org/images/vxhtml10" height="31" width="88"
align="right" border="0" alt="Valid XHTML 1.0!" /></a>
<a href="/feedback.html">Webmaster</a><br />
- $Date: 2001-07-14 22:19:59 $
+ $Date: 2001-07-24 10:18:31 $
</address>
</body>