W3C home > Mailing lists > Public > www-validator-cvs@w3.org > May 2004

validator/htdocs/config verbosemsg.cfg,1.1.2.10,1.1.2.11

From: Terje Bless <link@hutz.w3.org>
Date: Wed, 19 May 2004 05:24:21 +0000
To: www-validator-cvs@w3.org
Message-Id: <20040519052421.5EBBC481A@hutz.w3.org>

Update of /sources/public/validator/htdocs/config
In directory hutz:/tmp/cvs-serv23577

Modified Files:
      Tag: validator-0_6_0-branch
	verbosemsg.cfg 
Log Message:
Tweak explanation for entity reference errors (including cascade errors).


Index: verbosemsg.cfg
===================================================================
RCS file: /sources/public/validator/htdocs/config/Attic/verbosemsg.cfg,v
retrieving revision 1.1.2.10
retrieving revision 1.1.2.11
diff -u -d -r1.1.2.10 -r1.1.2.11
--- verbosemsg.cfg	19 May 2004 04:41:09 -0000	1.1.2.10
+++ verbosemsg.cfg	19 May 2004 05:24:17 -0000	1.1.2.11
@@ -90,6 +90,15 @@
 </msg>
 <msg 25>
   original = "general entity %1 not defined and no default entity"
+  verbose <<.EOF.
+  <div class="ve mid-25">
+    <p>
+      This is usually a cascading error caused by a an undefined entity
+      reference or use of an unencoded ampersand (&amp;) in an URL or body
+      text. See the previous message for further details.
+    </p>
+  </div>
+.EOF.  
 </msg>
 <msg 26>
   original = "RNI delimiter must be followed by name start character"
@@ -1169,6 +1178,15 @@
 </msg>
 <msg 325>
   original = "reference to entity %1 for which no system identifier could be generated"
+  verbose <<.EOF.
+  <div class="ve mid-325">
+    <p>
+      This is usually a cascading error caused by a an undefined entity
+      reference or use of an unencoded ampersand (&amp;) in an URL or body
+      text. See the previous message for further details.
+    </p>
+  </div>
+.EOF.  
 </msg>
 <msg 326>
   original = "entity was defined here"
@@ -1211,13 +1229,28 @@
   verbose <<.EOF.
   <div class="ve mid-338">
     <p>
-      You may have forgotten to "escape" an ampersand (&amp;) character, thus causing the validator
-      to believe that you created a new, undefined entity that starts with "&amp;".  
-      If you wish to cause an "&amp;" to appear within text or a URL, escape it by using "&amp;amp;".
+      An entity reference was found in the document, but there is no reference
+      by that name defined. Often this is caused by misspelling the reference
+      name, unencoded ampersands, or by leaving off the trailing semicolon (;).
+      <strong>The most common cause of this error is unencoded ampersands in
+      URLs</strong> as described by the <a
+        href="http://www.htmlhelp.com/">WDG</a> in "<a
+        href="http://www.htmlhelp.com/tools/validator/problems.html#amp">Ampersands
+        in URLs</a>".
     </p>
     <p>
-      Other possibilities: you actually wanted to use an entity, but misspelled it
-      (capitalization is important), or you forgot to close the entity with a semicolon.
+      Entity references start with an ampersand (&amp;) and end with a
+      semicolon (;). If you want to use a literal ampersand in your document
+      you must encode it as "&amp;amp;" (<em>even inside URLs!</em>). Be
+      careful to end entity references with a semicolon or your entity
+      reference may get interpreted in connection with the following text.
+      Also keep in mind that named entity references are case-sensitive;
+      &amp;Aelig; and &amp;aelig; are different characters.
+    </p>
+    <p>
+      Note that in most documents, errors related to entity references will
+      trigger up to 5 separate messages from the Validator. Usually these
+      will all disappear when the original problem is fixed.
     </p>
   </div>
 .EOF.
Received on Wednesday, 19 May 2004 01:35:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:02:06 UTC