Here are the validation results
Markup Validation Servicev0.6.7 Skip Navigation | Home About... News Docs
Help & FAQ Feedback Link Checker Jump To:
Results
File: Z:\index.htm
Encoding: windows-1252
Doctype: HTML 4.01 Transitional
Errors: 90
No DOCTYPE Found! Falling Back to HTML 4.01 TransitionalA DOCTYPE
Declaration is mandatory for most current markup languages and without one it
is impossible to reliably validate this document. I am falling back to "HTML
4.01 Transitional" and will attempt to validate the document anyway, but this
is very likely to produce spurious error messages for most non-trivial
documents.
So what should I do? Tell me more...
DOCTYPE Fallback in effect!
The DOCTYPE Declaration in your document was not recognized. This probably
means that the Formal Public Identifier contains a spelling error, or that
the Declaration is not using correct syntax. Validation has been performed
using a default "fallback" Document Type Definition that closely resembles
HTML 4.01 Transitional, but the document will not be Valid until you have
corrected the problem with the DOCTYPE Declaration.
This page is not Valid HTML 4.01 Transitional!
Below are the results of attempting to parse this document with an SGML
parser.
Line 1, column 0: no document type declaration; implying "<!DOCTYPE HTML
SYSTEM>"
<html>
The checked page did not contain a document type ("DOCTYPE") declaration.
The Validator has tried to validate with the HTML 4.01 Transitional DTD, but
this is quite likely to be incorrect and will generate a large number of
incorrect error messages. It is highly recommended that you insert the proper
DOCTYPE declaration in your document -- instructions for doing this are given
above -- and it is necessary to have this declaration before the page can be
declared to be valid.
✉
Line 11, column 111: value of attribute "NAME" must be a single token
....2/netw1111.css"><meta name="Microsoft Theme" content="network2 1111,
defaul..
✉
Line 12, column 21: value of attribute "NAME" must be a single token
<meta name="Microsoft Border" content="tlrb">
✉
Line 24, column 29: required attribute "TYPE" not specified
<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>.
✉
Line 34, column 44: required attribute "TYPE" not specified
// --></script><script language="JavaScript"><!--
✉
Line 36, column 44: there is no attribute "LANGUAGE"
..../script><a href="index.htm" language="JavaScript"
onmouseover="if(MSFPhover)
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.
✉
Line 36, column 341: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 38, column 385: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 40, column 371: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 42, column 368: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 44, column 387: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 46, column 391: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 48, column 367: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 50, column 358: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 52, column 387: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 54, column 437: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 56, column 388: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 58, column 399: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 60, column 377: required attribute "TYPE" not specified
....</a><br><script language="JavaScript"><!--
✉
Line 73, column 127: cannot generate system identifier for general entity "k"
......rsscalendar.com/rss/publish.asp?t=w&k=8c76acf2b5b98f72bec5c3e3b258f122&fw=46
An entity reference was found in the document, but there is no reference by
that name defined. Often this is caused by misspelling the reference name,
unencoded ampersands, or by leaving off the trailing semicolon (
. The most
common cause of this error is unencoded ampersands in URLs as described by
the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (
.
If you want to use a literal ampersand in your document you must encode it as
"&" (even inside URLs!). Be careful to end entity references with a semicolon
or your entity reference may get interpreted in connection with the following
text. Also keep in mind that named entity references are case-sensitive;
&Aelig; and æ are different characters.
Note that in most documents, errors related to entity references will
trigger up to 5 separate messages from the Validator. Usually these will all
disappear when the original problem is fixed.
✉
Line 73, column 127: general entity "k" not defined and no default entity
......rsscalendar.com/rss/publish.asp?t=w&k=8c76acf2b5b98f72bec5c3e3b258f122&fw=46
This is usually a cascading error caused by a an undefined entity reference
or use of an unencoded ampersand (&) in an URL or body text. See the previous
message for further details.
✉
Line 73, column 128: reference to entity "k" for which no system identifier
could be generated
.....rsscalendar.com/rss/publish.asp?t=w&k=8c76acf2b5b98f72bec5c3e3b258f122&fw=468
This is usually a cascading error caused by a an undefined entity reference
or use of an unencoded ampersand (&) in an URL or body text. See the previous
message for further details.
✉
Line 73, column 126: entity was defined here
.....w.rsscalendar.com/rss/publish.asp?t=w&k=8c76acf2b5b98f72bec5c3e3b258f122&fw=4
Line 73, column 162: cannot generate system identifier for general entity "fw"
.....w&k=8c76acf2b5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&e
✉
Line 73, column 162: general entity "fw" not defined and no default entity
.....w&k=8c76acf2b5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&e
✉
Line 73, column 164: reference to entity "fw" for which no system identifier
could be generated
.....k=8c76acf2b5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=
✉
Line 73, column 161: entity was defined here
.....=w&k=8c76acf2b5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&
Line 73, column 169: cannot generate system identifier for general entity "ff"
.....6acf2b5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFF
✉
Line 73, column 169: general entity "ff" not defined and no default entity
.....6acf2b5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFF
✉
Line 73, column 171: reference to entity "ff" for which no system identifier
could be generated
.....cf2b5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"
✉
Line 73, column 168: entity was defined here
.....76acf2b5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFF
Line 73, column 175: cannot generate system identifier for general entity "fs"
.....5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></s
✉
Line 73, column 175: general entity "fs" not defined and no default entity
.....5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></s
✉
Line 73, column 177: reference to entity "fs" for which no system identifier
could be generated
.....98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></scr
✉
Line 73, column 174: entity was defined here
.....b5b98f72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></
Line 73, column 181: cannot generate system identifier for general entity "fc"
.....2bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script>
✉
Line 73, column 181: general entity "fc" not defined and no default entity
.....2bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script>
✉
Line 73, column 183: reference to entity "fc" for which no system identifier
could be generated
.....ec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script><!
✉
Line 73, column 180: entity was defined here
.....72bec5c3e3b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script
Line 73, column 191: cannot generate system identifier for general entity "tb"
.....258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script><!--webbot
✉
Line 73, column 191: general entity "tb" not defined and no default entity
.....258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script><!--webbot
✉
Line 73, column 193: reference to entity "tb" for which no system identifier
could be generated
.....8f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script><!--webbot b
✉
Line 73, column 190: entity was defined here
.....b258f122&fw=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script><!--webbo
Line 73, column 201: cannot generate system identifier for general entity "eb"
....=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script><!--webbot
bot="HTML
✉
Line 73, column 201: general entity "eb" not defined and no default entity
....=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script><!--webbot
bot="HTML
✉
Line 73, column 203: reference to entity "eb" for which no system identifier
could be generated
....68&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script><!--webbot
bot="HTMLMa
✉
Line 73, column 200: entity was defined here
....w=468&ff=10&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script><!--webbot
bot="HTM
Line 73, column 211: required attribute "TYPE" not specified
....&fs=11&fc=000000&tb=ccc000&eb=FFFFFF"></script><!--webbot
bot="HTMLMarkup" en
✉
Line 77, column 11: there is no attribute "SRC"
<embed src="
http://www.aristanashville.com/radio/ka/468.swf" quality=high
plugin
✉
Line 77, column 69: there is no attribute "QUALITY"
....hville.com/radio/ka/468.swf" quality=high
pluginspage="
http://www.macromedia.
✉
Line 77, column 86: there is no attribute "PLUGINSPAGE"
....ka/468.swf" quality=high
pluginspage="
http://www.macromedia.com/shockwave/dow
✉
Line 77, column 179: there is no attribute "TYPE"
....P1_Prod_Version=ShockwaveFlash" type="application/x-shockwave-flash"
width="4
✉
Line 77, column 217: there is no attribute "WIDTH"
....application/x-shockwave-flash" width="468" height="60"></embed>
✉
Line 77, column 230: there is no attribute "HEIGHT"
....-shockwave-flash" width="468" height="60"></embed>
✉
Line 77, column 234: element "EMBED" undefined
....ckwave-flash" width="468" height="60"></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), or by using vendor proprietary extensions such as
"<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the
desired effect instead).
✉
Line 82, column 52: required attribute "ALT" not specified
<img src="WIRKFolder/sunsentinel.jpg" border="0"></a><br>
✉
Line 83, column 78: required attribute "ALT" not specified
.... src="WIRKFolder/indair.gif" border="0"></a><br>
✉
Line 85, column 46: required attribute "ALT" not specified
<img src="WIRKFolder/diala.gif" border="0"></a><p> </td>
✉
Line 86, column 184: cannot generate system identifier for general entity "t"
....ttp://infinity.medianext.com/b?e=153&t=12" border="0" alt="" width="125"
heig
✉
Line 86, column 184: general entity "t" not defined and no default entity
....ttp://infinity.medianext.com/b?e=153&t=12" border="0" alt="" width="125"
heig
✉
Line 86, column 185: reference to entity "t" for which no system identifier
could be generated
....tp://infinity.medianext.com/b?e=153&t=12" border="0" alt="" width="125"
heigh
✉
Line 86, column 183: entity was defined here
....
http://infinity.medianext.com/b?e=153&t=12" border="0" alt="" width="125"
hei
Line 93, column 14: there is no attribute "NAME"
<embed name="Store" src="Store.swf" quality="high" bgcolor="#333366"
✉
Line 93, column 61: there is no attribute "BGCOLOR"
....bed name="Store" src="Store.swf" quality="high" bgcolor="#333366"
✉
Line 96, column 103: element "EMBED" undefined
....x.cgi?P1_Prod_Version=ShockwaveFlash">
✉
Line 109, column 103: element "EMBED" undefined
....x.cgi?P1_Prod_Version=ShockwaveFlash">
✉
Line 122, column 103: element "EMBED" undefined
....x.cgi?P1_Prod_Version=ShockwaveFlash">
✉
Line 126, column 79: required attribute "ALT" not specified
....ndupwhite4.jpg" width="125" border="0"></a><br>
✉
Line 128, column 83: required attribute "ALT" not specified
....480000[1].jpg" width="125" border="0"></a><br>
✉
Line 133, column 69: required attribute "TYPE" not specified
....><!--webbot bot="HTMLMarkup" startspan --><style>
✉
Line 133, column 69: document type does not allow element "STYLE" here
....><!--webbot bot="HTMLMarkup" startspan --><style>
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 142, column 8: end tag for element "SCRIPT" which is not open
</script><noscript>Your browser does not support JavaScript. <a
title='RSS-to-Ja
The Validator found an end tag for the above element, but that element is
not currently open. This is often caused by a leftover end tag from an
element that was removed during editing, or by an implicitly closed element
(if you have an error related to an element being used where it is not
allowed, this is almost certainly the case). In the latter case this error
will disappear as soon as you fix the original problem.
If this error occured in a script section of your document, you should
probably read this FAQ entry.
✉
Line 142, column 303: end tag for element "A" which is not open
....ml=1>Click to read the latest news</a>.</noscript>
✉
Line 142, column 315: end tag for element "NOSCRIPT" which is not open
....o read the latest news</a>.</noscript>
✉
Line 143, column 123: end tag for element "A" which is not open
....Free RSS to JavaScript Converter'></a>
✉
Line 154, column 8: end tag for element "SCRIPT" which is not open
</script><noscript>Your browser does not support JavaScript. <a
title='RSS-to-Ja
✉
Line 154, column 311: end tag for element "A" which is not open
....ml=1>Click to read the latest news</a>.</noscript>
✉
Line 154, column 323: end tag for element "NOSCRIPT" which is not open
....o read the latest news</a>.</noscript>
✉
Line 155, column 123: end tag for element "A" which is not open
....Free RSS to JavaScript Converter'></a>
✉
Line 156, column 62: end tag for "STYLE" omitted, but its declaration does
not permit this
....bot bot="HTMLMarkup" endspan i-checksum="40002" --></td>
✉
Line 133, column 63: start tag was here
....ign="center"><!--webbot bot="HTMLMarkup" startspan --><style>
Line 162, column 49: required attribute "ALT" not specified
<img src="WIRKFolder/logoFdle.gif" border="0"><br>
✉
Line 166, column 49: required attribute "ALT" not specified
<img src="WIRKFolder/AAY-WIRK.jpg" border="0"></a></td>
✉
Line 172, column 121: required attribute "ALT" not specified
.... width="468" height="57" align="left"></a></td>
✉
Line 177, column 52: required attribute "ALT" not specified
<img src="WIRKFolder/AAMCO120x60.gif" border="0"></a></td>
✉
Line 225, column 23: end tag for element "TD" which is not open
<!--msnavigation--></td><td valign="top" width="24"></td><td valign="top"
width=
✉
Line 225, column 51: document type does not allow element "TD" here
<!--msnavigation--></td><td valign="top" width="24"></td><td valign="top"
width="1%">
✉
Line 225, column 84: document type does not allow element "TD" here
...."24"></td><td valign="top" width="1%">
✉
Line 228, column 9: end tag for element "TR" which is not open
</td></tr><!--msnavigation--></table><!--msnavigation--><table border="0"
cellpa
✉
Line 228, column 36: end tag for element "TABLE" which is not open
</td></tr><!--msnavigation--></table><!--msnavigation--><table border="0"
cellpa
✉
Feedback: The W3C Validator Team
Date: 2004/07/21 10:24:06 Copyright © 1994-2004 W3C® (MIT, ERCIM, Keio), All
Rights Reserved. W3C liability, trademark, document use and software
licensing rules apply. Your interactions with this site are in accordance
with our public and Member privacy statements.
Ronx said:
The entire page is surrounded by HTML markup webbot - this will
prevent any of the content being seen in Design view.
There are also some stray tags following the </body></html> tags - the
page needs to be validated.
--
Ron Symonds
Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
Mitch said:
http://www.wirk.com/index.htm
Jens Peter Karlsen said:
URL?
Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.
-----Original Message-----
From: Mitch [mailto:
[email protected]]
Posted At: 5. maj 2005 22:18
Posted To: microsoft.public.frontpage.programming
Conversation: Blank pages in normal mode
Subject: Blank pages in normal mode
I created a website using a modified theme. Looks great, but
when I went in to edit I only can view the nav bar and banner
in normal mode. Everything is there in html mode and in the
preview.
I don't know html and need the advantage of wysiwyg. Any help?
