WCM Forum - Einzelnen Beitrag anzeigen

Neo · 11.02.2005, 11:37

Zitat:

Below are the results of attempting to parse this document with an SGML parser.

1.

Line 1, column 0: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"

<HTML>

The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with the HTML 4.01 Transitional 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.

✉
2.

Line 3, column 9: end tag for "HEAD" which is not finished

</HEAD>

Most likely, You nested tags and closed them in the wrong order. For example

[i]...</p> is not acceptable, as [i] must be closed before

. Acceptable nesting is:

...</p>

Another possibility is that you used an element (e.g. 'ul') which requires a child element (e.g. 'li') that you did not include. Hence the parent element is "not finished", not complete.

✉
3.

Line 4, column 25: there is no attribute "FRAMEBORDER"

<FRAMESET frameborder="no" border="0" cols="*,5*">

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.

✉
4.

Line 4, column 37: there is no attribute "BORDER"

<FRAMESET frameborder="no" border="0" cols="*,5*">

✉
5.

Line 4, column 46: there is no attribute "COLS"

<FRAMESET frameborder="no" border="0" cols="*,5*">

✉
6.

Line 4, column 52: element "FRAMESET" undefined

<FRAMESET frameborder="no" border="0" cols="*,5*">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).

✉
7.

Line 5, column 17: there is no attribute "SRC"

<FRAME src="Data/thumbs.htm" NAME="Left Frame" scrolling="auto">

✉
8.

Line 5, column 40: there is no attribute "NAME"

<FRAME src="Data/thumbs.htm" NAME="Left Frame" scrolling="auto">

✉
9.

Line 5, column 63: there is no attribute "SCROLLING"

...AME src="Data/thumbs.htm" NAME="Left Frame" scrolling="auto">

✉
10.

Line 5, column 69: element "FRAME" undefined

...a/thumbs.htm" NAME="Left Frame" scrolling="auto">

✉
11.

Line 6, column 68: element "FRAME" undefined

...ata/page.htm" NAME="Right Frame" scrolling="auto">

✉
12.

Line 8, column 14: document type does not allow element "BODY" here

<BODY>

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).

✉
13.

Line 13, column 6: end tag for "HTML" which is not finished

</HTML>

✉

Nur so nebenbei - deine kleine Vergleichsseite weist 13 HTML-Fehler auf...