W3C home > Mailing lists > Public > www-validator@w3.org > February 2011

xhtml

From: Lee Mason <lee@isos.com>
Date: Wed, 23 Feb 2011 13:51:24 +0000
Message-Id: <C03B007F-CEAA-4A94-9F09-0B9A00F45C80@isos.com>
To: www-validator@w3.org
Hi, I just found some xHTML errors @ http://w3schools.com/htmldom/default.asp

Here are the errors the validator encountered - 

Line 221, Column 4: document type does not allow element "tr" here; assuming missing "table" start-tag
<tr><td align="center"><img border="0" src="htmltree.gif" alt="DOM HTML tree" w…
✉
 Line 268, Column 105: cannot generate system identifier for general entity "q"
…blank" rel="nofollow" href="http://www.altova.com/ref/?s=w3s_smspotlight&q=fo">
✉
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 (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). 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; &Aelig; and &aelig; are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

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.

 Line 268, Column 105: general entity "q" not defined and no default entity
…blank" rel="nofollow" href="http://www.altova.com/ref/?s=w3s_smspotlight&q=fo">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

 Line 268, Column 106: reference not terminated by REFC delimiter
…blank" rel="nofollow" href="http://www.altova.com/ref/?s=w3s_smspotlight&q=fo">
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

 Line 268, Column 106: reference to external entity in attribute value
…blank" rel="nofollow" href="http://www.altova.com/ref/?s=w3s_smspotlight&q=fo">
✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

 Line 268, Column 106: reference to entity "q" for which no system identifier could be generated
…blank" rel="nofollow" href="http://www.altova.com/ref/?s=w3s_smspotlight&q=fo">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

 Line 268, Column 104: entity was defined here
…blank" rel="nofollow" href="http://www.altova.com/ref/?s=w3s_smspotlight&q=fo">
 Line 272, Column 90: reference not terminated by REFC delimiter
…blank" rel="nofollow" href="http://www.altova.com/ref/?s=w3s_smspotlight&q=fo">
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

 Line 272, Column 90: reference to external entity in attribute value
…blank" rel="nofollow" href="http://www.altova.com/ref/?s=w3s_smspotlight&q=fo">
✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

 Line 272, Column 90: reference to entity "q" for which no system identifier could be generated
…blank" rel="nofollow" href="http://www.altova.com/ref/?s=w3s_smspotlight&q=fo">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

 Line 268, Column 104: entity was defined here
…blank" rel="nofollow" href="http://www.altova.com/ref/?s=w3s_smspotlight&q=fo">
 Line 429, Column 9: end tag for "td" omitted, but OMITTAG NO was specified
</center>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

 Line 93, Column 5: start tag was here
<tr><td align="center"><a name="top"></a>
 Line 429, Column 9: end tag for "tr" omitted, but OMITTAG NO was specified
</center>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

 Line 93, Column 1: start tag was here
<tr><td align="center"><a name="top"></a>
 Line 429, Column 9: end tag for "table" omitted, but OMITTAG NO was specified
</center>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

 Line 92, Column 1: start tag was here
<table style="width:960px;margin-top:0px;margin-bottom:0px;" border="0" cellpad…

Hope this helps!
Lee Mason 
Web Programmer
Website: http://www.isos.com/
Received on Wednesday, 23 February 2011 16:08:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:45 GMT