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, or other things affecting the output below. 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
(iso-8859-1)
is different from the value in the <meta> element
(iso-8859-15). I will use the
value from the HTTP header
(iso-8859-1) for this
validation.
Line 103,
Column 15:
NET-enabling start-tag requires SHORTTAG YES
<a href=images/stream.bmp><img src=images/stream.jpg width=370 height=320 borde…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 103,
Column 42:
NET-enabling start-tag requires SHORTTAG YES
…href=images/stream.bmp><img src=images/stream.jpg width=370 height=320 border=…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 103,
Column 42:
required attribute "ALT" not specified
…href=images/stream.bmp><img src=images/stream.jpg width=370 height=320 border=…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 127,
Column 18:
NET-enabling start-tag requires SHORTTAG YES
<img src=images/ipv6.jpg align=right width=150 height=150 />Já à algum tempo …
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 127,
Column 18:
required attribute "ALT" not specified
<img src=images/ipv6.jpg align=right width=150 height=150 />Já à algum tempo …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 127,
Column 177:
NET-enabling start-tag requires SHORTTAG YES
…l que se tenha aliado ao <a href=http://www.worldipv6launch.org>World IPv6 Lau…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 127,
Column 223:
end tag for element "A" which is not open
…nha aliado ao <a href=http://www.worldipv6launch.org>World IPv6 Launch</a>.<br>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 207,
Column 73:
cannot generate system identifier for general entity "m"
…id="paginas">Page:[58<a href="?pag=57&m=0"> 57</a><a href="?pag=56&m=0"> 56</a…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 207,
Column 73:
general entity "m" not defined and no default entity
…id="paginas">Page:[58<a href="?pag=57&m=0"> 57</a><a href="?pag=56&m=0"> 56</a…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 207,
Column 74:
reference to entity "m" for which no system identifier could be generated
…d="paginas">Page:[58<a href="?pag=57&m=0"> 57</a><a href="?pag=56&m=0"> 56</a>…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 207,
Column 72:
entity was defined here
… id="paginas">Page:[58<a href="?pag=57&m=0"> 57</a><a href="?pag=56&m=0"> 56</……?pag=57&m=0"> 57</a><a href="?pag=56&m=0"> 56</a><a href="?pag=55&m=0"> 55</a>…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 207,
Column 72:
entity was defined here
… id="paginas">Page:[58<a href="?pag=57&m=0"> 57</a><a href="?pag=56&m=0"> 56</……?pag=56&m=0"> 56</a><a href="?pag=55&m=0"> 55</a>]<br><Last <a href="?pag=1…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 207,
Column 72:
entity was defined here
… id="paginas">Page:[58<a href="?pag=57&m=0"> 57</a><a href="?pag=56&m=0"> 56</……="?pag=55&m=0"> 55</a>]<br><Last <a href="?pag=1&m=0">First> </a> </div><br>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 207,
Column 72:
entity was defined here
… id="paginas">Page:[58<a href="?pag=57&m=0"> 57</a><a href="?pag=56&m=0"> 56</…<a href=http://creativecommons.org/licenses/by-nc-nd/2.5/pt/>Copyright© 2004-20…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 213,
Column 85:
end tag for element "A" which is not open
…ativecommons.org/licenses/by-nc-nd/2.5/pt/>Copyright© 2004-2012</a><br><br><br>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 235,
Column 6:
end tag for element "DIV" which is not open
</div>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.
