Markup Validation Service

Validation Output: 8 Errors

1. Line 2959, Column 13: there is no attribute "COLOR"

   <font color=teal>

   ✉

   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 2959, Column 17: element "FONT" undefined

   <font color=teal>

   ✉

   You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
   • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
   • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
3. Line 3013, Column 12: there is no attribute "SIZE"

   <font size="+1"><tt>\n</tt></font>

   ✉

   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.

4. Line 3013, Column 16: element "FONT" undefined

   <font size="+1"><tt>\n</tt></font>

   ✉

   You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
   • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
   • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
5. Line 3181, Column 74: cannot generate system identifier for general entity "ixPost"

   …http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=75195" >

   ✉

   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.

6. Line 3181, Column 74: general entity "ixPost" not defined and no default entity

   …http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=75195" >

   ✉

   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.

7. Line 3181, Column 80: reference to entity "ixPost" for which no system identifier could be generated

   …http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=75195" >

   ✉

   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 3181, Column 73: entity was defined here

   …http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=75195" >

9. Line 3182, Column 72: reference to entity "ixPost" for which no system identifier could be generated

   	http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=75195

   ✉

   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.

10. Line 3181, Column 73: entity was defined here

    …http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=75195" >

11. Line 3247, Column 1: character data is not allowed here

    to that C file, rather than wait for it to break at run time.

    ✉

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.

↑ Top