Validation Output: 116 Errors

1. Line 5, Column 119: NET-enabling start-tag requires SHORTTAG YES

   …if" type="image/vnd.microsoft.icon" />

   ✉

   The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

2. Line 5, Column 120: character data is not allowed here

   …f" type="image/vnd.microsoft.icon" />

   ✉

   You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

   • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
   • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
   • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
3. Line 6, Column 148: NET-enabling start-tag requires SHORTTAG YES

   …ng und Züchtung von Prachtfinken. " />

   ✉

   The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

4. Line 7, Column 206: NET-enabling start-tag requires SHORTTAG YES

   …d,Rotkopfamadinen,Vögel,Vogelzucht" />

   ✉

   The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

5. Line 8, Column 36: NET-enabling start-tag requires SHORTTAG YES

   <meta name="author" content="Tüte" />

   ✉

   The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

6. Line 9, Column 44: NET-enabling start-tag requires SHORTTAG YES

   <meta name="robots" content="index,follow" />

   ✉

   The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

7. Line 159, Column 28: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

   <FONT color="white"><center>

   ✉

   The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

   One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

8. Line 160, Column 6: document type does not allow element "HEAD" here

   <head> 

   ✉

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

9. Line 161, Column 58: "T" is not a member of a group specified for any attribute

   …on" content="Mein Name ist Martin "Tüte" Noack. Seit 2006 beschäftige ich mic

   ✉

10. Line 161, Column 70: "NOACK." is not a member of a group specified for any attribute

    …"Mein Name ist Martin "Tüte" Noack. Seit 2006 beschäftige ich mich mit der Ha

    ✉

11. Line 161, Column 75: "SEIT" is not a member of a group specified for any attribute

    … Name ist Martin "Tüte" Noack. Seit 2006 beschäftige ich mich mit der Haltung

    ✉

12. Line 161, Column 75: "2006" is not a member of a group specified for any attribute

    … Name ist Martin "Tüte" Noack. Seit 2006 beschäftige ich mich mit der Haltung

    ✉

13. Line 161, Column 85: "BESCH" is not a member of a group specified for any attribute

    …Martin "Tüte" Noack. Seit 2006 beschäftige ich mich mit der Haltung und Zücht

    ✉

14. Line 161, Column 96: "ICH" is not a member of a group specified for any attribute

    …e" Noack. Seit 2006 beschäftige ich mich mit der Haltung und Züchtung von Pra

    ✉

15. Line 161, Column 101: "MICH" is not a member of a group specified for any attribute

    …ack. Seit 2006 beschäftige ich mich mit der Haltung und Züchtung von Prachtfi

    ✉

16. Line 161, Column 105: "MIT" is not a member of a group specified for any attribute

    … Seit 2006 beschäftige ich mich mit der Haltung und Züchtung von Prachtfinken

    ✉

17. Line 161, Column 109: "DER" is not a member of a group specified for any attribute

    …t 2006 beschäftige ich mich mit der Haltung und Züchtung von Prachtfinken."…

    ✉

18. Line 161, Column 117: "HALTUNG" is not a member of a group specified for any attribute

    …eschäftige ich mich mit der Haltung und Züchtung von Prachtfinken." />

    ✉

19. Line 161, Column 121: "UND" is not a member of a group specified for any attribute

    …äftige ich mich mit der Haltung und Züchtung von Prachtfinken." />

    ✉

20. Line 161, Column 122: "Z" is not a member of a group specified for any attribute

    …ftige ich mich mit der Haltung und Züchtung von Prachtfinken." />

    ✉

21. Line 161, Column 134: "VON" is not a member of a group specified for any attribute

    …ch mit der Haltung und Züchtung von Prachtfinken." />

    ✉

22. Line 161, Column 147: an attribute value literal can occur in an attribute specification list only after a VI delimiter

    …ltung und Züchtung von Prachtfinken." />

    ✉

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

23. Line 161, Column 149: character data is not allowed here

    …ung und Züchtung von Prachtfinken." />

    ✉

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
24. Line 162, Column 44: NET-enabling start-tag requires SHORTTAG YES

    <meta name="content-language" content="de" />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

25. Line 163, Column 45: NET-enabling start-tag requires SHORTTAG YES

    <meta name="revisit-after" content="5 days" />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

26. Line 165, Column 7: end tag for "HEAD" which is not finished

    </head>

    ✉

    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.

27. Line 167, Column 23: document type does not allow element "STYLE" here

    <style type="text/css">

    ✉

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

28. Line 183, Column 32: document type does not allow element "STYLE" here

    </style> <style type="text/css">

    ✉

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

29. Line 218, Column 23: document type does not allow element "STYLE" here

    <style type="text/css">

    ✉

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

30. Line 223, Column 23: document type does not allow element "STYLE" here

    <style type="text/css">

    ✉

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

31. Line 229, Column 23: document type does not allow element "STYLE" here

    <style type="text/css">

    ✉

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

32. Line 235, Column 23: document type does not allow element "STYLE" here

    <style type="text/css">

    ✉

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

33. Line 241, Column 23: document type does not allow element "STYLE" here

    <style type="text/css">

    ✉

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

34. Line 247, Column 23: document type does not allow element "STYLE" here

    <style type="text/css">

    ✉

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

35. Line 253, Column 23: document type does not allow element "STYLE" here

    <style type="text/css">

    ✉

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

36. Line 263, Column 8: NET-enabling start-tag requires SHORTTAG YES

    <center/><br></FONT>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

37. Line 263, Column 20: end tag for "CENTER" omitted, but its declaration does not permit this

    <center/><br></FONT>

    ✉

    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

38. Line 263: start tag was here

    ><center/><br></FONT>

39. Line 263, Column 20: end tag for "TABLE" omitted, but its declaration does not permit this

    <center/><br></FONT>

    ✉

    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

40. Line 260: start tag was here

    ><table border="0" width="70%" id="center">

41. Line 263, Column 20: end tag for "DIV" omitted, but its declaration does not permit this

    <center/><br></FONT>

    ✉

    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

42. Line 259: start tag was here

    ><div align="center">

43. Line 263, Column 20: end tag for "CENTER" omitted, but its declaration does not permit this

    <center/><br></FONT>

    ✉

    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

44. Line 159, Column 20: start tag was here

    <FONT color="white"><center>

45. Line 264, Column 23: document type does not allow element "STYLE" here

    <style type="text/css">

    ✉

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

46. Line 269, Column 15: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?

    <table height="102" id="ad-c9f0">

    ✉

    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.

47. Line 280, Column 85: Attribute "BACKGROUND" is not a valid attribute. Did you mean "background"?

    …class="edit_header_full" background="http://theme.webme.com/designs/iceblue/i

    ✉

    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.

48. Line 300, Column 73: end tag for "FONT" omitted, but its declaration does not permit this

    …ding"><font color="#570000">Navigation:</td>

    ✉

    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

49. Line 300, Column 35: start tag was here

    											<td class="nav_heading"><font color="#570000">Navigation:</td>

50. Line 304, Column 61: an attribute value must be a literal unless it contains only name characters

    …me.htm" class="menu"><b><font color=#570000>Home</font></b></a>											</…

    ✉

    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.

51. Line 312, Column 69: an attribute value must be a literal unless it contains only name characters

    …ch.htm" class="menu"><b><font color=#570000>Über mich</font></b></a>									

    ✉

    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.

52. Line 316, Column 70: an attribute value must be a literal unless it contains only name characters

    …en.htm" class="menu"><b><font color=#570000>Partnerseiten</font></b></a>					

    ✉

    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.

53. Line 324, Column 72: an attribute value must be a literal unless it contains only name characters

    …en.htm" class="menu"><b><font color=#500C05>Veranstaltungen</font></b></a>			

    ✉

    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.

54. Line 328, Column 78: an attribute value must be a literal unless it contains only name characters

    …in.htm" class="menu"><b><font color=#570000>Erfahrungen allgemein</font></b><

    ✉

    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.

55. Line 336, Column 79: an attribute value must be a literal unless it contains only name characters

    …nd.htm" class="menu"><b><font color=#570000>aktueller Vogelbestand</font></b>

    ✉

    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.

56. Line 340, Column 76: an attribute value must be a literal unless it contains only name characters

    …te.htm" class="menu"><b><font color=#570000>Vogelunterkünfte</font></b></a>		

    ✉

    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.

57. Line 348, Column 82: an attribute value must be a literal unless it contains only name characters

    …ka.htm" class="menu"><b><font color=#570000>Ex-Mitbewohner aus Afrika</font><

    ✉

    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.

58. Line 352, Column 86: an attribute value must be a literal unless it contains only name characters

    …en.htm" class="menu"><b><font color=#570000>Ex-Mitbewohner aus Australien</fo

    ✉

    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.

59. Line 356, Column 84: an attribute value must be a literal unless it contains only name characters

    …en.htm" class="menu"><b><font color=#570000>Ex-Mitbewohner aus Ozeanien</font

    ✉

    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.

60. Line 364, Column 73: an attribute value must be a literal unless it contains only name characters

    …09.htm" class="menu"><b><font color=#570000>Nachzuchten 2009</font></b></a>		

    ✉

    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.

61. Line 368, Column 73: an attribute value must be a literal unless it contains only name characters

    …10.htm" class="menu"><b><font color=#580000>Nachzuchten 2010</font></b></a>		

    ✉

    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.

62. Line 372, Column 75: an attribute value must be a literal unless it contains only name characters

    …er.htm" class="menu"><b><font color=#570000>andere Mitbewohner</font></b></a>

    ✉

    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.

63. Line 376, Column 76: an attribute value must be a literal unless it contains only name characters

    …he.htm" class="menu"><b><font color=#570000>Biete-Suche-Tausche</font></b></a

    ✉

    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.

64. Line 384, Column 69: an attribute value must be a literal unless it contains only name characters

    …ch.htm" class="menu"><b><font color=#570000>Bannertausch</font></b></a>						

    ✉

    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.

65. Line 388, Column 67: an attribute value must be a literal unless it contains only name characters

    …ng.htm" class="menu"><b><font color=#570000>Danksagung</font></b></a>								

    ✉

    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.

66. Line 392, Column 69: an attribute value must be a literal unless it contains only name characters

    …ch.htm" class="menu"><b><font color=#570000>Gästebuch</font></b></a>									

    ✉

    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.

67. Line 396, Column 64: an attribute value must be a literal unless it contains only name characters

    …kt.htm" class="menu"><b><font color=#570000>Kontakt</font></b></a>											

    ✉

    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.

68. Line 400, Column 108: required attribute "ALT" not specified

    …i_ende.gif" width="185" height="198">

    ✉

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

69. Line 433, Column 67: NET-enabling start-tag requires SHORTTAG YES

    …				<div style="width: 510; overflow: auto;"><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

70. Line 437, Column 143: NET-enabling start-tag requires SHORTTAG YES

    …pic/t/tuetesvogelwelt/linien_2.gif" /></td>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

71. Line 441, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

72. Line 442, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

73. Line 446, Column 419: NET-enabling start-tag requires SHORTTAG YES

    …gen zusammengefa&szlig;t werden.<br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

74. Line 451, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

75. Line 455, Column 125: NET-enabling start-tag requires SHORTTAG YES

    …tuetesvogelwelt/vogelhaeuschen.gif" /></td>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

76. Line 459, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

77. Line 460, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

78. Line 465, Column 185: NET-enabling start-tag requires SHORTTAG YES

    …">Alles f&uuml;r den Prachtfink!<br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

79. Line 466, Column 122: NET-enabling start-tag requires SHORTTAG YES

    …span style="font-size: medium;"><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

80. Line 467, Column 140: NET-enabling start-tag requires SHORTTAG YES

    …span style="font-size: medium;"><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

81. Line 468, Column 68: NET-enabling start-tag requires SHORTTAG YES

    …g.webme.com/smiles/grin.gif" alt="" /><img src="http://img.webme.com/smiles/g

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

82. Line 468, Column 125: NET-enabling start-tag requires SHORTTAG YES

    …g.webme.com/smiles/grin.gif" alt="" /><img src="http://img.webme.com/smiles/g

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

83. Line 468, Column 182: NET-enabling start-tag requires SHORTTAG YES

    …g.webme.com/smiles/grin.gif" alt="" /><img src="http://img.webme.com/smiles/g

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

84. Line 468, Column 239: NET-enabling start-tag requires SHORTTAG YES

    …g.webme.com/smiles/grin.gif" alt="" /><img src="http://img.webme.com/smiles/g

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

85. Line 468, Column 296: NET-enabling start-tag requires SHORTTAG YES

    …g.webme.com/smiles/grin.gif" alt="" /><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

86. Line 468, Column 302: NET-enabling start-tag requires SHORTTAG YES

    …e.com/smiles/grin.gif" alt="" /><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

87. Line 469, Column 92: NET-enabling start-tag requires SHORTTAG YES

    …span style="font-size: medium;"><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

88. Line 470, Column 107: NET-enabling start-tag requires SHORTTAG YES

    …etesvogelwelt/vogel_027.gif" alt="" /><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

89. Line 470, Column 113: NET-enabling start-tag requires SHORTTAG YES

    …gelwelt/vogel_027.gif" alt="" /><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

90. Line 476, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

91. Line 480, Column 139: NET-enabling start-tag requires SHORTTAG YES

    …d/der-talismann/note-09.gif" alt="" /></td>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

92. Line 488, Column 74: required attribute "TYPE" not specified

    …gn: center;"><script language="JavaScript">

    ✉

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

93. Line 493, Column 186: end tag for element "EMBED" which is not open

    …loop="true" autostart="true"></EMBED>');

    ✉

    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.

94. Line 499, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

95. Line 503, Column 143: NET-enabling start-tag requires SHORTTAG YES

    …pic/t/tuetesvogelwelt/linien_2.gif" /></td>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

96. Line 507, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /></div>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

97. Line 530, Column 45: document type does not allow element "H5" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

    																<font color="#570000"><b><h5><blink>Über einen Eintrag in mein

    ✉

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

98. Line 530, Column 52: element "BLINK" undefined. Did you mean "link" or "blockquote"?

    																<font color="#570000"><b><h5><blink>Über einen Eintrag in mein

    ✉

    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),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
99. Line 531, Column 44: end tag for "H5" omitted, but its declaration does not permit this

    Gästebuch würde ich mich sehr freuen!</font>

    ✉

    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

100. Line 530, Column 41: start tag was here

     																<font color="#570000"><b><h5><blink>Über einen Eintrag in mein

101. Line 531, Column 44: end tag for "B" omitted, but its declaration does not permit this

     Gästebuch würde ich mich sehr freuen!</font>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

102. Line 530, Column 38: start tag was here

     																<font color="#570000"><b><h5><blink>Über einen Eintrag in mein

103. Line 545, Column 71: end tag for "FONT" omitted, but its declaration does not permit this

     …ebar_heading"><font color="#570000">Time:</td>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

104. Line 545, Column 39: start tag was here

     											<td class="sidebar_heading"><font color="#570000">Time:</td>

105. Line 549, Column 65: required attribute "ALT" not specified

     …p://img.webme.com/pic/t/tuetesvogelwelt/breite.jpg">

     ✉

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

106. Line 551, Column 38: required attribute "TYPE" not specified

     <center><SCRIPT LANGUAGE="Javascript"><!--

     ✉

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

107. Line 555, Column 65: required attribute "ALT" not specified

     …p://img.webme.com/pic/t/tuetesvogelwelt/breite.jpg">											</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>.

108. Line 563, Column 71: end tag for "FONT" omitted, but its declaration does not permit this

     …ebar_heading"><font color="#570000">Huhu:</td>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

109. Line 563, Column 39: start tag was here

     											<td class="sidebar_heading"><font color="#570000">Huhu:</td>

110. Line 568, Column 65: required attribute "ALT" not specified

     …p://img.webme.com/pic/t/tuetesvogelwelt/breite.jpg">

     ✉

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

111. Line 569, Column 68: required attribute "ALT" not specified

     …g.webme.com/pic/t/tuetesvogelwelt/vogel_013.gif">

     ✉

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

112. Line 570, Column 5: NET-enabling start-tag requires SHORTTAG YES

     <br /><br />

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

113. Line 570, Column 11: NET-enabling start-tag requires SHORTTAG YES

     <br /><br />

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

114. Line 571, Column 65: required attribute "ALT" not specified

     …p://img.webme.com/pic/t/tuetesvogelwelt/breite.jpg">

     ✉

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

115. Line 572, Column 8: NET-enabling start-tag requires SHORTTAG YES

     <center/>											</td>

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

116. Line 572, Column 25: end tag for "CENTER" omitted, but its declaration does not permit this

     <center/>											</td>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

117. Line 572: start tag was here

     ><center/>											</td>

118. Line 572, Column 25: end tag for "CENTER" omitted, but its declaration does not permit this

     <center/>											</td>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

119. Line 567, Column 12: start tag was here

     												<center>

120. Line 580, Column 78: end tag for "FONT" omitted, but its declaration does not permit this

     …<font color="#570000">Bitte Voten:</td>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

121. Line 580, Column 39: start tag was here

     											<td class="sidebar_heading"><font color="#570000">Bitte Voten:</td>

122. Line 585, Column 65: required attribute "ALT" not specified

     …p://img.webme.com/pic/t/tuetesvogelwelt/breite.jpg">

     ✉

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

123. Line 586, Column 5: NET-enabling start-tag requires SHORTTAG YES

     <br /><br />

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

124. Line 586, Column 11: NET-enabling start-tag requires SHORTTAG YES

     <br /><br />

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

125. Line 587, Column 12: Attribute "SRC" is not a valid attribute. Did you mean "src"?

     <EMBED src='http://www.space-link.de/counter2.swf?idnr=5937' quality=high bgcolo

     ✉

     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.

126. Line 587, Column 70: Attribute "QUALITY" is not a valid attribute

     ….de/counter2.swf?idnr=5937' quality=high bgcolor=#000000  wmode=transparent  

     ✉

     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.

127. Line 587, Column 83: Attribute "BGCOLOR" is not a valid attribute. Did you mean "bgcolor"?

     …swf?idnr=5937' quality=high bgcolor=#000000  wmode=transparent  menu=false WI

     ✉

     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.

128. Line 587, Column 83: an attribute value must be a literal unless it contains only name characters

     …swf?idnr=5937' quality=high bgcolor=#000000  wmode=transparent  menu=false WI

     ✉

     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.

129. Line 587, Column 98: Attribute "WMODE" is not a valid attribute. Did you mean "code" or "frameborder"?

     …quality=high bgcolor=#000000  wmode=transparent  menu=false WIDTH=120 HEIGHT=

     ✉

     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.

130. Line 587, Column 116: Attribute "MENU" is not a valid attribute. Did you mean "onmouseup" or "onmouseout"?

     …or=#000000  wmode=transparent  menu=false WIDTH=120 HEIGHT=50 TYPE='applicati

     ✉

     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.

131. Line 587, Column 128: Attribute "WIDTH" is not a valid attribute. Did you mean "width"?

     …wmode=transparent  menu=false WIDTH=120 HEIGHT=50 TYPE='application/x-shockwa

     ✉

     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.

132. Line 587, Column 139: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?

     …parent  menu=false WIDTH=120 HEIGHT=50 TYPE='application/x-shockwave-flash'><

     ✉

     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.

133. Line 587, Column 147: Attribute "TYPE" is not a valid attribute. Did you mean "type"?

     …menu=false WIDTH=120 HEIGHT=50 TYPE='application/x-shockwave-flash'></EMBED>

     ✉

     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.

134. Line 587, Column 178: element "EMBED" undefined. Did you mean "meta" or "em"?

     …TYPE='application/x-shockwave-flash'></EMBED>

     ✉

     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),
     • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
     • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
135. Line 588, Column 5: NET-enabling start-tag requires SHORTTAG YES

     <br /><br />

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

136. Line 588, Column 11: NET-enabling start-tag requires SHORTTAG YES

     <br /><br />

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

137. Line 589, Column 65: required attribute "ALT" not specified

     …p://img.webme.com/pic/t/tuetesvogelwelt/breite.jpg">

     ✉

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

138. Line 590, Column 8: NET-enabling start-tag requires SHORTTAG YES

     <center/>											</td>

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

139. Line 590, Column 25: end tag for "CENTER" omitted, but its declaration does not permit this

     <center/>											</td>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

140. Line 590: start tag was here

     ><center/>											</td>

141. Line 590, Column 25: end tag for "CENTER" omitted, but its declaration does not permit this

     <center/>											</td>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

142. Line 584, Column 12: start tag was here

     												<center>

143. Line 598, Column 75: end tag for "FONT" omitted, but its declaration does not permit this

     …ding"><font color="#570000">Besucher:</td>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

144. Line 598, Column 39: start tag was here

     											<td class="sidebar_heading"><font color="#570000">Besucher:</td>

145. Line 603, Column 65: required attribute "ALT" not specified

     …p://img.webme.com/pic/t/tuetesvogelwelt/breite.jpg">

     ✉

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

146. Line 604, Column 111: NET-enabling start-tag requires SHORTTAG YES

     …55911523" border="0" alt=""></a><br /><a href="http://www.directcounter.de/st

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

147. Line 605, Column 65: required attribute "ALT" not specified

     …p://img.webme.com/pic/t/tuetesvogelwelt/breite.jpg">

     ✉

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

148. Line 606, Column 8: NET-enabling start-tag requires SHORTTAG YES

     <center/>											</td>

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

149. Line 606, Column 25: end tag for "CENTER" omitted, but its declaration does not permit this

     <center/>											</td>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

150. Line 606: start tag was here

     ><center/>											</td>

151. Line 606, Column 25: end tag for "CENTER" omitted, but its declaration does not permit this

     <center/>											</td>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

152. Line 602, Column 12: start tag was here

     												<center>

153. Line 624, Column 25: end tag for element "TD" which is not open

     <FONT color="white"></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.

154. Line 625, Column 5: end tag for element "TR" which is not open

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

155. Line 626, Column 8: end tag for element "TABLE" which is not open

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

156. Line 627, 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.

157. Line 628, Column 8: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

     <center>

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

158. Line 629, Column 5: NET-enabling start-tag requires SHORTTAG YES

     <br />

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

159. Line 630, Column 5: NET-enabling start-tag requires SHORTTAG YES

     <br />

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

160. Line 634, Column 211: NET-enabling start-tag requires SHORTTAG YES

     …nanzeigen.com/pictures/sticker.gif" /></a></td>

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

161. Line 635, Column 35: required attribute "TYPE" not specified

      <td><script language="JavaScript">function hit(hitlink) {if(document.images) {(

     ✉

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

162. Line 635, Column 400: NET-enabling start-tag requires SHORTTAG YES

     …rvoegel.de/topliste/img/banner.gif" /></a></td>

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

163. Line 636, Column 5: end tag for element "TD" which is not open

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

164. Line 644, Column 196: cannot generate system identifier for general entity "style"

     ….php?ref=www.tuetesvogelwelt.de.tl/&style=2" alt="www.180hits.de - Pagerank 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 "&amp;" (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 &aelig; 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.

165. Line 644, Column 196: general entity "style" not defined and no default entity

     ….php?ref=www.tuetesvogelwelt.de.tl/&style=2" alt="www.180hits.de - Pagerank 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.

166. Line 644, Column 201: reference to entity "style" for which no system identifier could be generated

     …ref=www.tuetesvogelwelt.de.tl/&style=2" alt="www.180hits.de - Pagerank Anzeig

     ✉

     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.

167. Line 644, Column 194: entity was defined here

     …nk.php?ref=www.tuetesvogelwelt.de.tl/&style=2" alt="www.180hits.de - Pagerank

168. Line 645, Column 225: reference to entity "style" for which no system identifier could be generated

     …php?ref=tuetesvogelwelt.de.tl/&style=1"  alt="pagerank.promotion-booster.de -

     ✉

     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.

169. Line 644, Column 194: entity was defined here

     …nk.php?ref=www.tuetesvogelwelt.de.tl/&style=2" alt="www.180hits.de - Pagerank

170. Line 647, Column 184: NET-enabling start-tag requires SHORTTAG YES

     …- Webmaster Portal" style="border:0"/></a></td>

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

171. Line 649, Column 70: required attribute "ALT" not specified

     …rver-seven.de/bilder/europalogo.gif"border="0">

     ✉

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

172. Line 654, Column 5: NET-enabling start-tag requires SHORTTAG YES

     <br />

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

173. Line 655, Column 5: NET-enabling start-tag requires SHORTTAG YES

     <br />

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

174. Line 656, Column 8: NET-enabling start-tag requires SHORTTAG YES

     <center/></FONT>

     ✉

     The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

175. Line 656, Column 16: end tag for "CENTER" omitted, but its declaration does not permit this

     <center/></FONT>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

176. Line 656: start tag was here

     ><center/></FONT>

177. Line 656, Column 16: end tag for "CENTER" omitted, but its declaration does not permit this

     <center/></FONT>

     ✉

     • You forgot to close a tag, or
     • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

     The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

178. Line 628: start tag was here

     ><center>

179. Line 657, Column 80: cannot generate system identifier for general entity "auth1"

     …de/cookie.php?visit=tuetesvogelwelt&auth1=38670d25db0eb3c1a6d1605a9b05bf3e&au

     ✉

     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 "&amp;" (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 &aelig; 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.

180. Line 657, Column 80: general entity "auth1" not defined and no default entity

     …de/cookie.php?visit=tuetesvogelwelt&auth1=38670d25db0eb3c1a6d1605a9b05bf3e&au

     ✉

     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.

181. Line 657, Column 85: reference to entity "auth1" for which no system identifier could be generated

     …okie.php?visit=tuetesvogelwelt&auth1=38670d25db0eb3c1a6d1605a9b05bf3e&auth2=5

     ✉

     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.

182. Line 657, Column 78: entity was defined here

     …n.de/cookie.php?visit=tuetesvogelwelt&auth1=38670d25db0eb3c1a6d1605a9b05bf3e&

183. Line 657, Column 119: cannot generate system identifier for general entity "auth2"

     …h1=38670d25db0eb3c1a6d1605a9b05bf3e&auth2=56277500c31ea4a39f901224fc00c5ba&au

     ✉

     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 "&amp;" (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 &aelig; 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.

184. Line 657, Column 119: general entity "auth2" not defined and no default entity

     …h1=38670d25db0eb3c1a6d1605a9b05bf3e&auth2=56277500c31ea4a39f901224fc00c5ba&au

     ✉

     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.

185. Line 657, Column 124: reference to entity "auth2" for which no system identifier could be generated

     …670d25db0eb3c1a6d1605a9b05bf3e&auth2=56277500c31ea4a39f901224fc00c5ba&auth3=3

     ✉

     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.

186. Line 657, Column 117: entity was defined here

     …uth1=38670d25db0eb3c1a6d1605a9b05bf3e&auth2=56277500c31ea4a39f901224fc00c5ba&

187. Line 657, Column 158: cannot generate system identifier for general entity "auth3"

     …h2=56277500c31ea4a39f901224fc00c5ba&auth3=3e0f8ab2966f3683dd8381073351ea29&au

     ✉

     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 "&amp;" (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 &aelig; 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.

188. Line 657, Column 158: general entity "auth3" not defined and no default entity

     …h2=56277500c31ea4a39f901224fc00c5ba&auth3=3e0f8ab2966f3683dd8381073351ea29&au

     ✉

     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.

189. Line 657, Column 163: reference to entity "auth3" for which no system identifier could be generated

     …277500c31ea4a39f901224fc00c5ba&auth3=3e0f8ab2966f3683dd8381073351ea29&auth4=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.

190. Line 657, Column 156: entity was defined here

     …uth2=56277500c31ea4a39f901224fc00c5ba&auth3=3e0f8ab2966f3683dd8381073351ea29&

191. Line 657, Column 197: cannot generate system identifier for general entity "auth4"

     …h3=3e0f8ab2966f3683dd8381073351ea29&auth4=a6dec4fb65f62739f18d9c59380346c6&au

     ✉

     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 "&amp;" (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 &aelig; 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.

192. Line 657, Column 197: general entity "auth4" not defined and no default entity

     …h3=3e0f8ab2966f3683dd8381073351ea29&auth4=a6dec4fb65f62739f18d9c59380346c6&au

     ✉

     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.

193. Line 657, Column 202: reference to entity "auth4" for which no system identifier could be generated

     …0f8ab2966f3683dd8381073351ea29&auth4=a6dec4fb65f62739f18d9c59380346c6&auth5=2

     ✉

     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.

194. Line 657, Column 195: entity was defined here

     …uth3=3e0f8ab2966f3683dd8381073351ea29&auth4=a6dec4fb65f62739f18d9c59380346c6&

195. Line 657, Column 236: cannot generate system identifier for general entity "auth5"

     …h4=a6dec4fb65f62739f18d9c59380346c6&auth5=252c98bc11c5619cf6b1d73530738c88&mo

     ✉

     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 "&amp;" (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 &aelig; 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.

196. Line 657, Column 236: general entity "auth5" not defined and no default entity

     …h4=a6dec4fb65f62739f18d9c59380346c6&auth5=252c98bc11c5619cf6b1d73530738c88&mo

     ✉

     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.

197. Line 657, Column 241: reference to entity "auth5" for which no system identifier could be generated

     …dec4fb65f62739f18d9c59380346c6&auth5=252c98bc11c5619cf6b1d73530738c88&mode=tr

     ✉

     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.

198. Line 657, Column 234: entity was defined here

     …uth4=a6dec4fb65f62739f18d9c59380346c6&auth5=252c98bc11c5619cf6b1d73530738c88&

199. Line 657, Column 275: cannot generate system identifier for general entity "mode"

     …h5=252c98bc11c5619cf6b1d73530738c88&mode=track" style="display:none;width:1px

     ✉

     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 "&amp;" (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 &aelig; 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.

200. Line 657, Column 275: general entity "mode" not defined and no default entity

     …h5=252c98bc11c5619cf6b1d73530738c88&mode=track" style="display:none;width:1px

     ✉

     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.

201. Line 657, Column 279: reference to entity "mode" for which no system identifier could be generated

     …52c98bc11c5619cf6b1d73530738c88&mode=track" style="display:none;width:1px;hei

     ✉

     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.

202. Line 657, Column 273: entity was defined here

     …uth5=252c98bc11c5619cf6b1d73530738c88&mode=track" style="display:none;width:1

↑ Top