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.
No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.
Line 165,
Column 92:
cannot generate system identifier for general entity "ct"
…<a href="/002.aspx?dqa=0:0:0:72:0:0:-1:0:0&ct=111">relatórios de contas</a></b>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 165,
Column 92:
general entity "ct" not defined and no default entity
…<a href="/002.aspx?dqa=0:0:0:72:0:0:-1:0:0&ct=111">relatórios de contas</a></b>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 165,
Column 94:
reference not terminated by REFC delimiter
…<a href="/002.aspx?dqa=0:0:0:72:0:0:-1:0:0&ct=111">relatórios de contas</a></b>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 165,
Column 94:
reference to external entity in attribute value
…<a href="/002.aspx?dqa=0:0:0:72:0:0:-1:0:0&ct=111">relatórios de contas</a></b>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 165,
Column 94:
reference to entity "ct" for which no system identifier could be generated
…<a href="/002.aspx?dqa=0:0:0:72:0:0:-1:0:0&ct=111">relatórios de contas</a></b>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 165,
Column 91:
entity was defined here
…<a href="/002.aspx?dqa=0:0:0:72:0:0:-1:0:0&ct=111">relatórios de contas</a></b>