Дубль...три!

Result: Failed validation, 65 errors
File: menu.htm
Encoding: windows-1251
Doctype: (no Doctype found)
No DOCTYPE found! Attempting validation with HTML 4.01 Transitional.
The DOCTYPE Declaration was not recognized or is missing. This probably means that the Formal Public Identifier contains a spelling error, or that the Declaration is not using correct syntax. Validation has been performed using a default "fallback" Document Type Definition that closely resembles "HTML 4.01 Transitional", but the document will not be Valid until you have corrected this problem with the DOCTYPE Declaration.
Learn how to add a doctype to your document from our FAQ.
This page is not Valid (no Doctype found)!
Below are the results of attempting to parse this document with an SGML parser.
Error Line 1 column 0: no document type declaration; implying "".
The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
✉
Error Line 7 column 6: end tag for element "HEAD" which is not open.
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 occured in a script section of your document, you should probably read this FAQ entry.
✉
Error Line 9 column 5: document type does not allow element "BODY" here.
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).
✉
Error Line 12 column 29: required attribute "TYPE" not specified.
var loc = '';
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 and type="text/javascript" for .
✉
Error Line 13 column 32: required attribute "TYPE" not specified.
try{ var loc = escape(top.location.href); }catc
✉
Error Line 14 column 29: required attribute "TYPE" not specified.
✉
Error Line 19 column 269: end tag for element "A" which is not open.
..."Saratov Banner Network" border=0>');
✉
Error Line 19 column 278: end tag for element "IFRAME" which is not open.
...Banner Network" border=0>');
✉
Warning Line 33 column 60: cannot generate system identifier for general entity "ZK238U5ARI".
... id=me href='mann.pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'
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.
✉
Error Line 33 column 60: general entity "ZK238U5ARI" not defined and no default entity.
... id=me href='mann.pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'
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.
✉
Error Line 33 column 70: reference to entity "ZK238U5ARI" for which no system identifier could be generated.
...f='mann.pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Перс�
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.
✉
Info Line 33 column 59: entity was defined here.
...a id=me href='mann.pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content
Warning Line 33 column 71: cannot generate system identifier for general entity "from".
...='mann.pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персо
✉
Error Line 33 column 71: general entity "from" not defined and no default entity.
...='mann.pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персо
✉
Error Line 33 column 75: reference to entity "from" for which no system identifier could be generated.
...nn.pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персона
✉
Info Line 33 column 70: entity was defined here.
...f='mann.pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Перс�
Warning Line 33 column 78: cannot generate system identifier for general entity "p".
...pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персонал�
✉
Error Line 33 column 78: general entity "p" not defined and no default entity.
...pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персонал�
✉
Error Line 33 column 79: reference to entity "p" for which no system identifier could be generated.
...l?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персональ
✉
Info Line 33 column 77: entity was defined here.
....pl?u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персонал
Warning Line 33 column 82: cannot generate system identifier for general entity "on".
...=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персональн�
✉
Error Line 33 column 82: general entity "on" not defined and no default entity.
...=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персональн�
✉
Error Line 33 column 84: reference to entity "on" for which no system identifier could be generated.
...nac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персональна�
✉
Info Line 33 column 81: entity was defined here.
...u=pnac%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персональн
Warning Line 33 column 87: cannot generate system identifier for general entity "op".
...%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персональная �
✉
Error Line 33 column 87: general entity "op" not defined and no default entity.
...%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персональная �
✉
Error Line 33 column 89: reference to entity "op" for which no system identifier could be generated.
...Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персональная и�
✉
Info Line 33 column 86: entity was defined here.
...c%5Fspirit&ZK238U5ARI&from=0&p=3&on=0&op=0#content'>Персональная
Error Line 36 column 27: ID "ME" already defined.
Настройки ча
✉
Error Line 36 column 72: general entity "go" not defined and no default entity.
...'setts.pl?u=pnac%5Fspirit&ZK238U5ARI&go=make#content'>Настройки ча
✉
Error Line 36 column 74: reference to entity "go" for which no system identifier could be generated.
...etts.pl?u=pnac%5Fspirit&ZK238U5ARI&go=make#content'>Настройки чат
✉
Info Line 36 column 71: entity was defined here.
...='setts.pl?u=pnac%5Fspirit&ZK238U5ARI&go=make#content'>Настройки ч�
Error Line 39 column 27: ID "ME" already defined.
✉
Info Line 93 column 88: entity was defined here.
...sid=67164&bn=0&target=blank&bt=1&pz=0&rnd=1271838085" frameborder=0 vspace=0
Error Line 95 column 59: reference to entity "bn" for which no system identifier could be generated.
...river.ru/cgi-bin/rle.cgi?sid=67164&bn=0&bt=1&pz=0&rnd=1271838085" alt="-AdRiv
✉
Info Line 93 column 60: entity was defined here.
...adriver.ru/cgi-bin/erle.cgi?sid=67164&bn=0&target=blank&bt=1&pz=0&rnd=1271838
Error Line 95 column 64: reference to entity "bt" for which no system identifier could be generated.
....ru/cgi-bin/rle.cgi?sid=67164&bn=0&bt=1&pz=0&rnd=1271838085" alt="-AdRiver-"
✉
Info Line 93 column 78: entity was defined here.
.../erle.cgi?sid=67164&bn=0&target=blank&bt=1&pz=0&rnd=1271838085" frameborder=0
Error Line 95 column 69: reference to entity "pz" for which no system identifier could be generated.
...gi-bin/rle.cgi?sid=67164&bn=0&bt=1&pz=0&rnd=1271838085" alt="-AdRiver-" borde
✉
Info Line 93 column 83: entity was defined here.
....cgi?sid=67164&bn=0&target=blank&bt=1&pz=0&rnd=1271838085" frameborder=0 vspa
Error Line 95 column 75: reference to entity "rnd" for which no system identifier could be generated.
.../rle.cgi?sid=67164&bn=0&bt=1&pz=0&rnd=1271838085" alt="-AdRiver-" border=0 wi
✉
Info Line 93 column 88: entity was defined here.
...sid=67164&bn=0&target=blank&bt=1&pz=0&rnd=1271838085" frameborder=0 vspace=0
Error Line 99 column 84: required attribute "TYPE" not specified.
...unter-->document.write('

Комментарии

Дубль...три!

Комментарии

Новый комментарий