Markup Validation Service

Validation Output: 4 Errors

1. Line 19, Column 56: there is no attribute "BORDER"

   …ge/2005_participant_trans.gif" border="0" alt="Official NaNoWriMo 2005 Partici…

   ✉

   You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

   This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

   How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

2. Line 19, Column 102: NET-enabling start-tag requires SHORTTAG YES

   …_participant_trans.gif" border="0" alt="Official NaNoWriMo 2005 Participant" />

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

3. Line 782, Column 80: cannot generate system identifier for general entity "cat"

   …tp://www.livescience.com/bestimg/?url=myths_10percent_brain_03.jpg&cat=myths" >

   ✉

   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.

4. Line 782, Column 80: general entity "cat" not defined and no default entity

   …tp://www.livescience.com/bestimg/?url=myths_10percent_brain_03.jpg&cat=myths" >

   ✉

   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.

5. Line 782, Column 83: reference to entity "cat" for which no system identifier could be generated

   …tp://www.livescience.com/bestimg/?url=myths_10percent_brain_03.jpg&cat=myths" >

   ✉

   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.

6. Line 782, Column 79: entity was defined here

   …tp://www.livescience.com/bestimg/?url=myths_10percent_brain_03.jpg&cat=myths" >

7. Line 783, Column 73: reference to entity "cat" for which no system identifier could be generated

   http://www.livescience.com/bestimg/?url=myths_10percent_brain_03.jpg&cat=myths

   ✉

   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.

8. Line 782, Column 79: entity was defined here

   …tp://www.livescience.com/bestimg/?url=myths_10percent_brain_03.jpg&cat=myths" >

↑ Top