Syntax error in: http://www.uba.be/nl/hf
http://www.uba.be/nl/hf
Rare constructie voor een table element.
Tnx!
73,
Ivo
----------------
- Line 369, Column 36: document type does not allow element "td" here
<td width="30%" class="rteleft">
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).
- Line 371, Column 93: Attribute "border" exists, but can not be used for this element.
…f?" alt="Status" width="121" border="1" height="21"></a>
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.
- Line 371, Column 112: end tag for "img" omitted, but OMITTAG NO was specified
…dth="121" border="1" height="21"></a>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 371, Column 6: start tag was here
<img src="http://www.n3kl.org/sun/images/status.gif?" alt="Status" width="
- Line 373, Column 37: document type does not allow element "td" here
<td width="20%" class="rteright">
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).
- Line 376, Column 36: document type does not allow element "td" here
<td width="30%" class="rteleft">
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).
- Line 378, Column 114: end tag for "img" omitted, but OMITTAG NO was specified
…dth="121" border="1" height="21"></a>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 378, Column 6: start tag was here
<img src="http://www.n3kl.org/sun/images/kpstatus.gif?" alt="Status" width
- Line 380, Column 7: end tag for "td" omitted, but OMITTAG NO was specified
</tr>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 367, Column 4: start tag was here
<td width="20%" class="rteright">
- Line 388, Column 93: end tag for "br" omitted, but OMITTAG NO was specified
…blank">Announced DXpeditions</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 388, Column 88: start tag was here
…et="_blank">Announced DXpeditions</a><br>
- Line 389, Column 75: end tag for "br" omitted, but OMITTAG NO was specified
… target="_blank">DX 425 News</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 389, Column 70: start tag was here
…ww.425dxn.org/" target="_blank">DX 425 News</a><br>
- Line 390, Column 87: end tag for "br" omitted, but OMITTAG NO was specified
…rget="_blank">OP DX Bulletin</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 390, Column 82: start tag was here
…l" target="_blank">OP DX Bulletin</a><br>
- Line 391, Column 86: end tag for "br" omitted, but OMITTAG NO was specified
…et="_blank">ARRL DX Bulletin</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 391, Column 81: start tag was here
… target="_blank">ARRL DX Bulletin</a><br>
- Line 392, Column 120: end tag for "br" omitted, but OMITTAG NO was specified
…blank">DX Bulletin de XE1BEF</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 392, Column 115: start tag was here
…et="_blank">DX Bulletin de XE1BEF</a><br>
- Line 393, Column 96: end tag for "br" omitted, but OMITTAG NO was specified
…rget="_blank">DX News Letter</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 393, Column 91: start tag was here
…m" target="_blank">DX News Letter</a><br>
- Line 394, Column 76: end tag for "br" omitted, but OMITTAG NO was specified
…get="_blank">The DX Notebook</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 394, Column 71: start tag was here
….dxer.org" target="_blank">The DX Notebook</a><br>
- Line 395, Column 109: end tag for "br" omitted, but OMITTAG NO was specified
…Worldwide list of HF beacons</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 395, Column 104: start tag was here
…ank">Worldwide list of HF beacons</a><br>
- Line 398, Column 77: end tag for "br" omitted, but OMITTAG NO was specified
…" target="_blank">DX Central</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 398, Column 72: start tag was here
…x-central.com" target="_blank">DX Central</a><br>
- Line 399, Column 91: end tag for "br" omitted, but OMITTAG NO was specified
…>DL2CC/DH3SBX QSL Mgr engine</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 399, Column 86: start tag was here
…lank">DL2CC/DH3SBX QSL Mgr engine</a><br>
- Line 400, Column 114: end tag for "br" omitted, but OMITTAG NO was specified
…"_blank">K3WWP's QSL Engines</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 400, Column 109: start tag was here
…rget="_blank">K3WWP's QSL Engines</a><br>
- Line 401, Column 96: end tag for "br" omitted, but OMITTAG NO was specified
…k">IK3QAR QSL Manager engine</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 401, Column 91: start tag was here
…_blank">IK3QAR QSL Manager engine</a><br>
- Line 402, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
…rise-sunset times world wide</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 402, Column 110: start tag was here
…y sunrise-sunset times world wide</a><br>
- Line 403, Column 111: end tag for "br" omitted, but OMITTAG NO was specified
…lank">Local times world wide</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 403, Column 106: start tag was here
…t="_blank">Local times world wide</a><br>
- Line 404, Column 98: end tag for "br" omitted, but OMITTAG NO was specified
…"_blank">K4UTE Prefix Finder</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 404, Column 93: start tag was here
…rget="_blank">K4UTE Prefix Finder</a><br>
- Line 405, Column 108: end tag for "br" omitted, but OMITTAG NO was specified
…et="_blank">Propagatie F6CRP</a><…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 405, Column 103: start tag was here
… target="_blank">Propagatie F6CRP</a><br>
- Line 436, Column 29: Attribute "hspace" exists, but can not be used for this element.
<td><img hspace="10" height="121" width="61" align="left" alt="" rel
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.
- Line 436, Column 64: Attribute "align" exists, but can not be used for this element.
…="10" height="121" width="61" align="left" alt="" rel="lightbox" src="/sites/
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.
- Line 436, Column 82: Attribute "rel" exists, but can not be used for this element.
… width="61" align="left" alt="" rel="lightbox" src="/sites/default/files/pics
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.
- Line 707, Column 262: end tag for "img" omitted, but OMITTAG NO was specified
…tes/all/modules/spamspan/image.gif"><span class="d">darc [dot] de</span></spa
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 707, Column 192: start tag was here
…pamspan"><span class="u">dc9xu</span><img alt="at" width="10" src="/sites/all
- Line 371, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 371 and a
…ges/status.gif?" alt="Status" width="121" border="1" height="21"></a>…
- Line 372, Column 9: XML Parsing Error: Opening and ending tag mismatch: a line 370 and td
</td>
- Line 378, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 378 and a
…ges/kpstatus.gif?" alt="Status" width="121" border="1" height="21"></a>…
- Line 379, Column 9: XML Parsing Error: Opening and ending tag mismatch: a line 377 and td
</td>
- Line 380, Column 7: XML Parsing Error: Opening and ending tag mismatch: td line 376 and tr
</tr>
- Line 381, Column 8: XML Parsing Error: Opening and ending tag mismatch: td line 369 and tbody
</tbody></table>
- Line 381, Column 16: XML Parsing Error: Opening and ending tag mismatch: td line 367 and table
</tbody></table>
- Line 382, Column 6: XML Parsing Error: Opening and ending tag mismatch: tr line 366 and div
</div>
- Line 396, Column 9: XML Parsing Error: Opening and ending tag mismatch: br line 395 and td
</td>
- Line 406, Column 9: XML Parsing Error: Opening and ending tag mismatch: br line 405 and td
</td>
- Line 407, Column 7: XML Parsing Error: Opening and ending tag mismatch: br line 404 and tr
</tr>
- Line 408, Column 8: XML Parsing Error: Opening and ending tag mismatch: br line 403 and tbody
</tbody></table>
- Line 408, Column 16: XML Parsing Error: Opening and ending tag mismatch: br line 402 and table
</tbody></table>
- Line 409, Column 6: XML Parsing Error: Opening and ending tag mismatch: br line 401 and div
</div>
- Line 707, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 707 and span
…bmit nominations to Stadt Bad Bentheim, Schloßstr. 2, D-48455 Bad Benth…
- Line 708, Column 10: XML Parsing Error: Opening and ending tag mismatch: span line 707 and p
</p>
- Line 719, Column 16: XML Parsing Error: Opening and ending tag mismatch: p line 707 and div
</p></div>
- Line 888, Column 6: XML Parsing Error: Opening and ending tag mismatch: br line 400 and div
</div>
- Line 889, Column 20: XML Parsing Error: Opening and ending tag mismatch: br line 399 and div
</div>
- Line 890, Column 18: XML Parsing Error: Opening and ending tag mismatch: br line 398 and div
</div>
- Line 892, Column 16: XML Parsing Error: Opening and ending tag mismatch: td line 397 and div
</div>
- Line 893, Column 14: XML Parsing Error: Opening and ending tag mismatch: br line 394 and div
</div>
- Line 896, Column 12: XML Parsing Error: Opening and ending tag mismatch: br line 393 and div
</div>
- Line 909, Column 8: XML Parsing Error: Opening and ending tag mismatch: br line 392 and div
</div>
- Line 910, Column 8: XML Parsing Error: Opening and ending tag mismatch: br line 391 and div
</div>
- Line 911, Column 9: XML Parsing Error: Opening and ending tag mismatch: br line 390 and body
</body>
- Line 912, Column 7: XML Parsing Error: Opening and ending tag mismatch: br line 389 and html
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag br line 388
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag td line 387
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag tr line 386
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag tbody line 385
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag table line 384
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 383
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag tbody line 365
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag table line 364
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 363
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 315
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 306
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 304
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 295
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 293
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 269
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 189
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 105
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag div line 104
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag body line 102
</html>
- Line 912, Column 7: XML Parsing Error: Premature end of data in tag html line 2
</html>
- Login to post comments