Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Character Encoding mismatch!
The character encoding specified in the HTTP header
(utf-8)
is different from the value in the <meta> element
(iso-8859-1). I will use the
value from the HTTP header
(utf-8) for this
validation.
Line 6, Column 13:
Attribute "type" exists, but can not be used for this element.
<STYLE type=text/css media=all>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.
Line 6, Column 13:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<STYLE type=text/css media=all><STYLE type=text/css media=all>This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).
Line 6, Column 18:
element "STYLE" undefined. Did you mean "style"?
<STYLE type=text/css media=all>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:
Line 7, Column 1:
character data is not allowed here
@import url( http://media.blackducksoftware.com/koders/styles/koders_home.css );You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 8, Column 8:
end tag for element "STYLE" which is not open
</STYLE>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 63, Column 14:
Attribute "type" exists, but can not be used for this element.
<SCRIPT type=text/javascript>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.
Line 63, Column 14:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<SCRIPT type=text/javascript><SCRIPT type=text/javascript>This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).
Line 63, Column 19:
element "SCRIPT" undefined. Did you mean "script"?
<SCRIPT type=text/javascript>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:
Line 64, Column 14:
end tag for element "SCRIPT" which is not open
</SCRIPT>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 67, Column 5:
Attribute "src" exists, but can not be used for this element.
src="http://media.blackducksoftware.com/koders/scripts/twoLevelScript.js" 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.
Line 68, Column 6:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
type=text/javascript></SCRIPT>type=text/javascript></SCRIPT>This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).
Line 68, Column 11:
element "SCRIPT" undefined. Did you mean "script"?
type=text/javascript></SCRIPT>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:
Line 68, Column 30:
end tag for element "SCRIPT" which is not open
type=text/javascript></SCRIPT>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 69, Column 13:
Attribute "title" exists, but can not be used for this element.
<LINK title="rss 2.0" href="/rss.xml" type=application/rss+xml rel=alternate>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.
Line 69, Column 28:
Attribute "href" exists, but can not be used for this element.
<LINK title="rss 2.0" href="/rss.xml" type=application/rss+xml rel=alternate>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.
Line 69, Column 44:
Attribute "type" exists, but can not be used for this element.
<LINK title="rss 2.0" href="/rss.xml" type=application/rss+xml rel=alternate>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.
Line 69, Column 44:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<LINK title="rss 2.0" href="/rss.xml" type=application/rss+xml rel=alternate><LINK title="rss 2.0" href="/rss.xml" type=application/rss+xml rel=alternate>This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).
Line 69, Column 56:
element "LINK" undefined. Did you mean "link"?
<LINK title="rss 2.0" href="/rss.xml" type=application/rss+xml rel=alternate>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:
Line 70, Column 15:
Attribute "content" exists, but can not be used for this element.
<META content="MSHTML 6.00.2900.3527" name=GENERATOR>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.
Line 70, Column 44:
Attribute "name" exists, but can not be used for this element.
<META content="MSHTML 6.00.2900.3527" name=GENERATOR>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.
Line 70, Column 44:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<META content="MSHTML 6.00.2900.3527" name=GENERATOR><META content="MSHTML 6.00.2900.3527" name=GENERATOR>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:
Line 76, Column 7:
end tag for "META" omitted, but OMITTAG NO was specified
</head>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 70:
start tag was here
><META content="MSHTML 6.00.2900.3527" name=GENERATOR><TABLE id=container cellSpacing=0 cellPadding=0 width="950" align=center 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.
Line 83, Column 11:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TABLE id=container cellSpacing=0 cellPadding=0 width="950" align=center <TABLE id=container cellSpacing=0 cellPadding=0 width="950" align=center 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.
Line 83, Column 33:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TABLE id=container cellSpacing=0 cellPadding=0 width="950" align=center <TABLE id=container cellSpacing=0 cellPadding=0 width="950" align=center 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.
Line 83, Column 47:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TABLE id=container cellSpacing=0 cellPadding=0 width="950" align=center <TABLE id=container cellSpacing=0 cellPadding=0 width="950" align=center 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.
Line 83, Column 67:
Attribute "align" exists, but can not be used for this element.
…er cellSpacing=0 cellPadding=0 width="950" align=center 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.
Line 83, Column 67:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
…er cellSpacing=0 cellPadding=0 width="950" align=center border=0><TBODY>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.
Line 84, Column 10:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
border=0><TBODY> border=0><TBODY>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:
Line 84, Column 18:
element "TBODY" undefined. Did you mean "tbody"?
border=0><TBODY>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:
Line 85, Column 6:
element "TR" undefined. Did you mean "tr"?
<TR>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:
Line 86, Column 16:
Attribute "vAlign" is not a valid attribute. Did you mean "valign"?
<TD vAlign=top width="950" height=92>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.
Line 86, Column 16:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD vAlign=top width="950" height=92> <TD vAlign=top width="950" height=92>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.
Line 86, Column 39:
Attribute "height" exists, but can not be used for this element.
<TD vAlign=top width="950" height=92>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.
Line 86, Column 39:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD vAlign=top width="950" height=92> <TD vAlign=top width="950" height=92>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:
Line 87, Column 18:
Attribute "class" exists, but can not be used for this element.
<DIV class=header_row>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.
Line 87, Column 18:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<DIV class=header_row> <DIV class=header_row>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:
Line 88, Column 20:
Attribute "class" exists, but can not be used for this element.
<TABLE class=header_row id=header_table cellSpacing=0 cellPadding=0 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.
Line 88, Column 20:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TABLE class=header_row id=header_table cellSpacing=0 cellPadding=0 <TABLE class=header_row id=header_table cellSpacing=0 cellPadding=0 <TABLE class=header_row id=header_table cellSpacing=0 cellPadding=0 … id=header_table cellSpacing=0 cellPadding=0 width="950" border=0> width="950" border=0>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:
Line 90, Column 15:
element "TBODY" undefined. Did you mean "tbody"?
<TBODY>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:
Line 91, Column 12:
element "TR" undefined. Did you mean "tr"?
<TR>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:
Line 92, Column 21:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD width=268 rowSpan=2><!-- <div id='duck_home_link'><a href="/"><img <TD width=268 rowSpan=2><!-- <div id='duck_home_link'><a href="/"><imgYou 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.
Line 92, Column 33:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD width=268 rowSpan=2><!-- <div id='duck_home_link'><a href="/"><img <TD width=268 rowSpan=2><!-- <div id='duck_home_link'><a href="/"><imgYou 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:
Line 93, Column 16:
Attribute "id" exists, but can not be used for this element.
id=duck_home_link href="/"><IMG 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.
Line 93, Column 16:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
id=duck_home_link href="/"><IMG id=duck_home_link href="/"><IMG 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.
Line 93, Column 39:
element "A" undefined. Did you mean "a"?
id=duck_home_link href="/"><IMG 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:
Line 94, Column 20:
Attribute "height" exists, but can not be used for this element.
height=92 width=268 alt="" 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.
Line 94, Column 20:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
height=92 width=268 alt="" height=92 width=268 alt="" 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.
Line 94, Column 29:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
height=92 width=268 alt="" height=92 width=268 alt="" 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.
Line 95, Column 17:
Attribute "src" exists, but can not be used for this element.
src="http://media.blackducksoftware.com/koders/images/bds_koders_logYou 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.
Line 95, Column 87:
element "IMG" undefined. Did you mean "img"?
…m/koders/images/bds_koders_logo.jpg"></A></TD>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:
Line 95, Column 91:
end tag for "IMG" omitted, but OMITTAG NO was specified
…ders/images/bds_koders_logo.jpg"></A></TD>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 39:
start tag was here
id=duck_home_link href="/"><IMG <TD height=92> <TD height=92>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:
Line 98, Column 12:
element "TR" undefined. Did you mean "tr"?
<TR><TD height=0>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:
Line 98, Column 24:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TR><TD height=0> <TR><TD height=0>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:
Line 99, Column 21:
Attribute "id" exists, but can not be used for this element.
<DIV id=nav_container>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.
Line 99, Column 21:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<DIV id=nav_container> <DIV id=nav_container>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:
Line 100, Column 23:
Attribute "class" exists, but can not be used for this element.
<UL class=main_nav>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.
Line 100, Column 23:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<UL class=main_nav> <UL class=main_nav>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:
Line 101, Column 26:
Attribute "class" exists, but can not be used for this element.
<LI class=top_level><A 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.
Line 101, Column 26:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<LI class=top_level><A <LI class=top_level><A 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:
Line 102, Column 51:
element "A" undefined. Did you mean "a"?
href="http://corp.koders.com/about/"><IMG class=rollovers 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:
Line 102, Column 63:
Attribute "class" exists, but can not be used for this element.
… href="http://corp.koders.com/about/"><IMG class=rollovers 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.
Line 102, Column 63:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
… href="http://corp.koders.com/about/"><IMG class=rollovers id=learn_rollover alt="" 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.
Line 103, Column 18:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
id=learn_rollover alt="" …/koders/images/about_button_top.gif"></A> 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:
Line 104, Column 94:
end tag for "IMG" omitted, but OMITTAG NO was specified
…ers/images/about_button_top.gif"></A> 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 102, Column 51:
start tag was here
href="http://corp.koders.com/about/"><IMG class=rollovers <UL>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:
Line 107, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 108, Column 46:
Attribute "title" exists, but can not be used for this element.
<div align="left"><A title="About Koders.com" 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.
Line 109, Column 53:
element "A" undefined. Did you mean "a"?
href="http://corp.koders.com/about/">About</A> </div>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:
Line 111, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 113, Column 60:
element "A" undefined. Did you mean "a"?
href="http://corp.koders.com/about#Contact"> 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:
Line 115, Column 25:
element "LI" undefined. Did you mean "li"?
</LI><LI>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:
Line 117, Column 54:
element "A" undefined. Did you mean "a"?
href="http://corp.koders.com/sitemap"> 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:
Line 120, Column 19:
end tag for element "ul" which is not open
</ul></li>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 120, Column 24:
end tag for element "li" which is not open
</ul></li>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 122, Column 25:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<LI class=top_level><A <LI class=top_level><A 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:
Line 123, Column 54:
element "A" undefined. Did you mean "a"?
href="http://corp.koders.com/resources"><IMG 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:
Line 124, Column 21:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
class=rollovers id=resources_rollover alt="" class=rollovers id=resources_rollover alt="" …ers/images/resources_button_top.gif"></A> 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:
Line 125, Column 98:
end tag for "IMG" omitted, but OMITTAG NO was specified
…images/resources_button_top.gif"></A> 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 123, Column 54:
start tag was here
href="http://corp.koders.com/resources"><IMG <UL>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:
Line 128, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 130, Column 56:
element "A" undefined. Did you mean "a"?
href="http://corp.koders.com/resources"> 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:
Line 133, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 135, Column 69:
element "A" undefined. Did you mean "a"?
…"http://corp.koders.com/resources/license-info">License Info</A> 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:
Line 137, Column 25:
element "LI" undefined. Did you mean "li"?
</LI><LI>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:
Line 139, Column 69:
element "A" undefined. Did you mean "a"?
…"http://corp.koders.com/resources/top-searches">Top Searches</A> 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:
Line 141, Column 25:
element "LI" undefined. Did you mean "li"?
</LI><LI>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:
Line 143, Column 64:
element "A" undefined. Did you mean "a"?
… href="http://corp.koders.com/resources/widgets">Add search to your site</A> 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:
Line 145, Column 25:
element "LI" undefined. Did you mean "li"?
</LI><LI>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:
Line 147, Column 65:
element "A" undefined. Did you mean "a"?
… href="http://corp.koders.com/resources/feedback">Feedback</A> 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:
Line 150, Column 6:
end tag for element "ul" which is not open
</ul></li>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 150, Column 11:
end tag for element "li" which is not open
</ul></li>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 151, Column 25:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<LI class=top_level><A <LI class=top_level><A 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:
Line 152, Column 54:
element "A" undefined. Did you mean "a"?
href="http://corp.koders.com/downloads"><IMG 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:
Line 153, Column 21:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
class=rollovers id=products_rollover alt="" class=rollovers id=products_rollover alt="" …ers/images/community_button_top.gif"></A> 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:
Line 154, Column 98:
end tag for "IMG" omitted, but OMITTAG NO was specified
…images/community_button_top.gif"></A> 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 152, Column 54:
start tag was here
href="http://corp.koders.com/downloads"><IMG <UL>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:
Line 157, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 159, Column 56:
element "A" undefined. Did you mean "a"?
href="http://corp.koders.com/downloads"> 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:
Line 162, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 164, Column 61:
element "A" undefined. Did you mean "a"?
… href="http://corp.koders.com/downloads/demo">Demo 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:
Line 166, Column 25:
element "LI" undefined. Did you mean "li"?
</LI><LI>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:
Line 168, Column 64:
element "A" undefined. Did you mean "a"?
… href="http://corp.koders.com/downloads/plugins">Plugins</A> </div>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:
Line 169, Column 25:
element "LI" undefined. Did you mean "li"?
</LI><LI>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:
Line 171, Column 68:
element "A" undefined. Did you mean "a"?
…f="http://corp.koders.com/downloads/plugins#IDE">IDE Plugins</A> </div>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:
Line 172, Column 25:
element "LI" undefined. Did you mean "li"?
</LI><LI>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:
Line 174, Column 72:
element "A" undefined. Did you mean "a"?
…//corp.koders.com/downloads/plugins#browser">Browser Plugins</A> </div>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:
Line 176, Column 19:
end tag for element "ul" which is not open
</ul></li>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 176, Column 24:
end tag for element "li" which is not open
</ul></li>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 177, Column 25:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<LI class=top_level><A <LI class=top_level><A 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:
Line 178, Column 61:
element "A" undefined. Did you mean "a"?
… href="http://corp.koders.com/support/overview"><IMG class=rollovers 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:
Line 178, Column 73:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
…rp.koders.com/support/overview"><IMG class=rollovers id=news_rollover alt="" …oders/images/support_button_top.gif"></A> 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:
Line 180, Column 96:
end tag for "IMG" omitted, but OMITTAG NO was specified
…s/images/support_button_top.gif"></A> 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 178, Column 61:
start tag was here
… href="http://corp.koders.com/support/overview"><IMG class=rollovers <UL>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:
Line 183, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 185, Column 63:
element "A" undefined. Did you mean "a"?
… href="http://corp.koders.com/support/overview">Overview</A> </div>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:
Line 187, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 189, Column 70:
element "A" undefined. Did you mean "a"?
…ttp://corp.koders.com/support/getting-started">Getting Started Guide</A> </div>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:
Line 190, Column 25:
element "LI" undefined. Did you mean "li"?
</LI><LI>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:
Line 192, Column 77:
element "A" undefined. Did you mean "a"?
…ers.com/support/getting-started#search">Search Examples</A> </div>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:
Line 194, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 196, Column 70:
element "A" undefined. Did you mean "a"?
…ttp://corp.koders.com/support/contact-support">Contact Support</A> </div>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:
Line 199, Column 7:
end tag for element "ul" which is not open
</ul></li>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 199, Column 12:
end tag for element "li" which is not open
</ul></li>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 200, Column 25:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<LI class=top_level><A <LI class=top_level><A 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:
Line 201, Column 63:
Attribute "target" exists, but can not be used for this element.
… href="http://www.blackducksoftware.com/" target="_blank"><IMG 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.
Line 201, Column 71:
element "A" undefined. Did you mean "a"?
…//www.blackducksoftware.com/" target="_blank"><IMG 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:
Line 202, Column 21:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
class=rollovers id=blackduck_rollover alt="" class=rollovers id=blackduck_rollover alt="" …om/koders/images/bds_button_top.gif"></A> 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:
Line 203, Column 92:
end tag for "IMG" omitted, but OMITTAG NO was specified
…oders/images/bds_button_top.gif"></A> 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 201, Column 71:
start tag was here
…//www.blackducksoftware.com/" target="_blank"><IMG <UL>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:
Line 206, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 208, Column 116:
element "A" undefined. Did you mean "a"?
…Black Duck Software" target="_blank">About Black Duck Software</A></div>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:
Line 210, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 212, Column 118:
element "A" undefined. Did you mean "a"?
…he Black Duck Suite" target="_blank">The Black Duck Suite</A> </div>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:
Line 214, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 217, Column 49:
element "A" undefined. Did you mean "a"?
title="OSS Page" target="_blank">Open Source Resource Center</A> </div>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:
Line 219, Column 20:
element "LI" undefined. Did you mean "li"?
<LI>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:
Line 221, Column 118:
element "A" undefined. Did you mean "a"?
…ck Knowledge Center" target="_blank">Black Duck Knowledge Center</A> </div>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:
Line 222, Column 25:
element "LI" undefined. Did you mean "li"?
</LI><LI>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:
Line 224, Column 102:
element "A" undefined. Did you mean "a"?
…act" title="Contact" target="_blank">Contact</A> </div>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:
Line 227, Column 25:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<LI class=top_level><A <LI class=top_level><A 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:
Line 228, Column 58:
element "A" undefined. Did you mean "a"?
href="http://corp.koders.com/submitproject"><IMG 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:
Line 229, Column 104:
Attribute "name" exists, but can not be used for this element.
…/submit_button_top.gif" alt="" name="company_rollover" border="0" class=rolloYou 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.
Line 229, Column 130:
Attribute "border" exists, but can not be used for this element.
…t="" name="company_rollover" border="0" class=rollovers 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.
Line 229, Column 140:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
…"company_rollover" border="0" class=rollovers id=company_rollover></A></LI> id=company_rollover></A></LI>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:
Line 230, Column 38:
end tag for "IMG" omitted, but OMITTAG NO was specified
id=company_rollover></A></LI>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 228, Column 58:
start tag was here
href="http://corp.koders.com/submitproject"><IMG </UL></DIV></TD>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 177, Column 14:
start tag was here
<LI class=top_level><A </UL></DIV></TD>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 156, Column 14:
start tag was here
<UL></UL></DIV></TD>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 151, Column 14:
start tag was here
<LI class=top_level><A </UL></DIV></TD>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 127, Column 14:
start tag was here
<UL></UL></DIV></TD>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 122, Column 14:
start tag was here
<LI class=top_level><A </UL></DIV></TD>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 106, Column 14:
start tag was here
<UL></UL></DIV></TD>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 101, Column 15:
start tag was here
<LI class=top_level><A </UL></DIV></TD>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 100, Column 12:
start tag was here
<UL class=main_nav> </TR></TBODY></TABLE></DIV></TD></TD></TR>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 234, Column 6:
element "TR" undefined. Did you mean "tr"?
<TR>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:
Line 235, Column 16:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD vAlign=top align=left height=7 bgcolor=#cc3300 colSpan=2></TD></TR> <TD vAlign=top align=left height=7 bgcolor=#cc3300 colSpan=2></TD></TR>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.
Line 235, Column 26:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD vAlign=top align=left height=7 bgcolor=#cc3300 colSpan=2></TD></TR> <TD vAlign=top align=left height=7 bgcolor=#cc3300 colSpan=2></TD></TR> <TD vAlign=top align=left height=7 bgcolor=#cc3300 colSpan=2></TD></TR>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.
Line 235, Column 48:
an attribute value must be a literal unless it contains only name characters
<TD vAlign=top align=left height=7 bgcolor=#cc3300 colSpan=2></TD></TR>You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 235, Column 64:
Attribute "colSpan" is not a valid attribute. Did you mean "colspan"?
…ign=top align=left height=7 bgcolor=#cc3300 colSpan=2></TD></TR>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.
Line 235, Column 64:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
…ign=top align=left height=7 bgcolor=#cc3300 colSpan=2></TD></TR>…n=top align=left height=7 bgcolor=#cc3300 colSpan=2></TD></TR>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:
Line 236, Column 6:
element "TR" undefined. Did you mean "tr"?
<TR>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:
Line 237, Column 16:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD vAlign=center align=left bgColor=#ffffff colSpan=2><!-- end content tabl <TD vAlign=center align=left bgColor=#ffffff colSpan=2><!-- end content tabl…TD vAlign=center align=left bgColor=#ffffff colSpan=2><!-- end content table 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.
Line 237, Column 42:
an attribute value must be a literal unless it contains only name characters
…TD vAlign=center align=left bgColor=#ffffff colSpan=2><!-- end content table You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 237, Column 58:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD vAlign=center align=left bgColor=#ffffff colSpan=2><!-- end content table --> <TD vAlign=center align=left bgColor=#ffffff colSpan=2><!-- end content table -->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:
Line 243, Column 53:
document type does not allow element "form" here
<form action="default.aspx" method="get">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 244, Column 18:
document type does not allow element "tr" here; assuming missing "table" start-tag
<tr> <input name=s type="text" size="60" maxlength="100" /> </form>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 244, Column 14:
start tag was here
<tr> </table>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 330, Column 12:
end tag for element "p" which is not open
</p> </td>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 336, Column 40:
Attribute "height" exists, but can not be used for this element.
<tr bgcolor="#f19f37" height="30" width="555">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.
Line 336, Column 51:
Attribute "width" exists, but can not be used for this element.
<tr bgcolor="#f19f37" height="30" width="555">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.
Line 350, Column 148:
required attribute "alt" not specified
…d_rule.gif" width="950" height="7" /></td>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 362, Column 259:
required attribute "alt" not specified
…width="199" height="23" border="0" /></a></div></td>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 364, Column 246:
required attribute "alt" not specified
…width="199" height="23" border="0" /></a></div></td>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 366, Column 257:
required attribute "alt" not specified
…width="199" height="23" border="0" /></a></div></td>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 374, Column 191:
required attribute "alt" not specified
…d_rule.gif" width="2" height="235" /></div></td>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 408, Column 191:
required attribute "alt" not specified
…d_rule.gif" width="2" height="235" /></div></td>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 412, Column 191:
required attribute "alt" not specified
…d_rule.gif" width="2" height="235" /></div></td>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 417, Column 143:
required attribute "alt" not specified
…tware.com/koders/images/spacer.gif"/><img src="http://media.blackducksoftwareThe attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 417, Column 244:
required attribute "alt" not specified
…r_bar.gif" width="950" height="17" /></td>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 426, Column 6:
element "TR" undefined. Did you mean "tr"?
<TR>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:
Line 427, Column 16:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD vAlign=center align=left bgColor=#ffffff colSpan=2> <TD vAlign=center align=left bgColor=#ffffff colSpan=2> <TD vAlign=center align=left bgColor=#ffffff colSpan=2>You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 427, Column 58:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD vAlign=center align=left bgColor=#ffffff colSpan=2> <TD vAlign=center align=left bgColor=#ffffff colSpan=2>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:
Line 428, Column 16:
Attribute "align" exists, but can not be used for this element.
<P align=center><A href="http://corp.koders.com/about/" class="k_footer">AYou 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.
Line 428, Column 16:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<P align=center><A href="http://corp.koders.com/about/" class="k_footer">A <P align=center><A href="http://corp.koders.com/about/" class="k_footer">AYou 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:
Line 428, Column 69:
Attribute "class" exists, but can not be used for this element.
…><A href="http://corp.koders.com/about/" class="k_footer">About Koders</A> | <A 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.
Line 428, Column 79:
element "A" undefined. Did you mean "a"?
…p.koders.com/about/" class="k_footer">About Koders</A> | <A 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:
Line 429, Column 63:
element "A" undefined. Did you mean "a"?
…f="http://corp.koders.com/resources" class="k_footer">Resources</A> | <AYou 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:
Line 430, Column 64:
element "A" undefined. Did you mean "a"?
…"http://corp.koders.com/downloads/" class="k_footer">Downloads</A> | <A 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:
Line 431, Column 71:
element "A" undefined. Did you mean "a"?
…oders.com/support/overview/" class="k_footer">Support</A> | <A 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:
Line 432, Column 80:
element "A" undefined. Did you mean "a"?
…m/" target="_blank" class="k_footer">Black Duck</A> | <A 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:
Line 433, Column 67:
element "A" undefined. Did you mean "a"?
…//corp.koders.com/submitproject" class="k_footer">Submit Project</A> | <A 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:
Line 434, Column 71:
element "A" undefined. Did you mean "a"?
…oders.com/terms-of-service/" class="k_footer">Terms of Service </A> | <A 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:
Line 435, Column 59:
element "A" undefined. Did you mean "a"?
href="http://corp.koders.com/DMCA/" class="k_footer">DMCA</A> | <A 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:
Line 436, Column 69:
element "A" undefined. Did you mean "a"?
…rp.koders.com/privacy-policy/" class="k_footer">Privacy Policy</A> | <A 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:
Line 437, Column 62:
element "A" undefined. Did you mean "a"?
…ref="http://corp.koders.com/sitemap/" class="k_footer">Site Map</A>| <A 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:
Line 438, Column 67:
element "A" undefined. Did you mean "a"?
…//corp.koders.com/about#Contact" class="k_footer">Contact Us</A></P></TD></TR>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:
Line 439, Column 6:
element "TR" undefined. Did you mean "tr"?
<TR>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:
Line 440, Column 16:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD vAlign=center align=left bgColor=#ffffff colSpan=2> <TD vAlign=center align=left bgColor=#ffffff colSpan=2> <TD vAlign=center align=left bgColor=#ffffff colSpan=2>You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 440, Column 58:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD vAlign=center align=left bgColor=#ffffff colSpan=2> <TD vAlign=center align=left bgColor=#ffffff colSpan=2>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:
Line 441, Column 26:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TABLE cellSpacing=0 cellPadding=0 width=950 border=0> <TABLE cellSpacing=0 cellPadding=0 width=950 border=0> <TABLE cellSpacing=0 cellPadding=0 width=950 border=0> <TABLE cellSpacing=0 cellPadding=0 width=950 border=0> <TABLE cellSpacing=0 cellPadding=0 width=950 border=0>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:
Line 442, Column 15:
element "TBODY" undefined. Did you mean "tbody"?
<TBODY>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:
Line 443, Column 12:
element "TR" undefined. Did you mean "tr"?
<TR>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:
Line 444, Column 23:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<TD colSpan=2> <TD colSpan=2>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:
Line 445, Column 41:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<div align="center"><DIV id=footer_div> <div align="center"><DIV id=footer_div>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:
Line 447, Column 12:
end tag for element "DIV" which is not open
</DIV></DIV></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 447, Column 17:
end tag for "div" omitted, but OMITTAG NO was specified
</DIV></DIV></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>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 445, Column 12:
start tag was here
<div align="center"><DIV id=footer_div></body>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 80, Column 2:
start tag was here
<div align="center"><STYLE type=text/css media=all><STYLE type=text/css media=all><STYLE type=text/css media=all></STYLE><SCRIPT type=text/javascript><SCRIPT type=text/javascript><SCRIPT type=text/javascript> </SCRIPT>