"No character encoding found, No doctype found"

Vanilla · Dec 12, 2005

Thanks Ronx for suggesting http://www.w3schools.com. It is an excellent site
for beginners. I spent my whole day there. This is where Iâ€™ve got my next
question.
I validated my website and at the first time I had 180 errors. Somehow with
the websiteâ€™s recommendations Iâ€™m down to 10 errors from which I cannot
improve anymore. I pasted the result of the latest validation. It is a
great comfort knowing that somebody always has the answer.

Validation result
using http://www.w3schools.com
Result: Failed validation, 10 errors.
Encoding: utf-8
Doctype: (no Doctype found)
Help on the options is available.
No Character Encoding Found! Falling back to UTF-8.
I was not able to extract a character encoding labeling from any of the
valid sources for such information. Without encoding information it is
impossible to reliably validate the document. I'm falling back to the "UTF-8"
encoding and will attempt to perform the validation, but this is likely to
fail for all non-trivial documents.
Read the FAQ entry on character encoding for more details
and pointers on how to fix this problem with your document.
This page is not Valid (no Doctype found)!

Below are the results of attempting to parse this document with an SGML
parser.
1. Error Line 1 column 74: character "<" invalid: only minimum data
characters allowed.
....henginelcoator//DTD HTML 4.01 Transitional/<html>
âœ‰
2. Error Line 1 column 79: character ">" invalid: only minimum data
characters allowed.
....ator//DTD HTML 4.01 Transitional/<html>
âœ‰
3. Error Line 2 column 0: character "<" invalid: only minimum data
characters allowed.
<html>
âœ‰
4. Error Line 2 column 5: character ">" invalid: only minimum data
characters allowed.
<html>
âœ‰
5. Error Line 4 column 0: character "<" invalid: only minimum data
characters allowed.
<head>
âœ‰
6. Error Line 4 column 5: character ">" invalid: only minimum data
characters allowed.
<head>
âœ‰
7. Error Line 5 column 0: character "<" invalid: only minimum data
characters allowed.
<meta http-equiv="Content-Language" content="en-us"><meta
http-equiv="Content-Ty
âœ‰
8. Error Line 5 column 17: invalid formal public identifier
"-//searchenginelcoator//DTD HTML 4.01 Transitional/html html head meta
http-equiv=": missing //.
<meta http-equiv="Content-Language" content="en-us"><meta
http-equiv="Content-Ty
âœ‰
9. Error Line 5 column 18: "CONTENT-LANGUAGE" is not a reserved name.
<meta http-equiv="Content-Language" content="en-us"><meta
http-equiv="Content-Ty
âœ‰
10. Error Line 5 column 18: cannot continue because of previous errors.
<meta http-equiv="Content-Language" content="en-us"><meta
http-equiv="Content-Ty

Murray · Dec 12, 2005

Result: Failed validation, 10 errors.

Encoding: utf-8
Doctype: (no Doctype found)
Help on the options is available.
No Character Encoding Found! Falling back to UTF-8.

Try this for the first 4 lines of your page -

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

Vanilla · Dec 12, 2005

I thought that I followed your instructions, but probably I'm doing something
wrong, because I am back to 182 errors! Here is the result. I appriciate
your help.
Result--just part of it--: Failed validation, 182 errors
Address:
Encoding: iso-8859-1 (detect automatically) utf-8 (Unicode, worldwide)
utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central
Europe) iso-8859-3 (Southern Europe) iso-8859-4 (Baltic Rim) iso-8859-5
(Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8-i (Hebrew)
iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-13 (Latin 7) iso-8859-14
(Celtic) iso-8859-15 (Latin 9) us-ascii (basic English) euc-jp (Japanese,
Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr
(Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5
(Chinese, traditional) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian)
macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic)
windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish)
windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)
Doctype: (no Doctype found) (detect automatically) XHTML 1.1 XHTML Basic
1.0 XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset ISO/IEC
15445:2000 ("ISO HTML") HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01
Frameset HTML 3.2 HTML 2.0 MathML 2.0 XHTML 1.1 plus MathML 2.0
Revalidate With Options: Show Source Show Outline
Show Parse Tree ...no attributes
Validate error pages Verbose Output

Help on the options is available.

No DOCTYPE found! Attempting validation with HTML 4.01 Transitional. The
DOCTYPE Declaration was not recognized or is missing. This probably means
that the Formal Public Identifier contains a spelling error, or that the
Declaration is not using correct syntax. Validation has been performed using
a default "fallback" Document Type Definition that closely resembles "HTML
4.01 Transitional", but the document will not be Valid until you have
corrected this problem with the DOCTYPE Declaration.

Learn how to add a doctype to your document from our FAQ.

This page is not Valid (no Doctype found)!
Below are the results of attempting to parse this document with an SGML
parser.

Error Line 1 column 0: no document type declaration; implying "<!DOCTYPE
HTML SYSTEM>".
<html><head><meta http-equiv="Content-Type" content="text/html;
charset=iso-8859
The checked page did not contain a document type ("DOCTYPE") declaration.
The Validator has tried to validate with a fallback DTD, but this is quite
likely to be incorrect and will generate a large number of incorrect error
messages. It is highly recommended that you insert the proper DOCTYPE
declaration in your document -- instructions for doing this are given above
-- and it is necessary to have this declaration before the page can be
declared to be valid.

âœ‰

Error Line 1 column 216: there is no attribute "TOPMARGIN".
....ad><body bgcolor="#E6E6FF" topmargin="00"><table cellpadding="0"
cellspacing=
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.

âœ‰

Error Line 1 column 279: there is no attribute "HEIGHT".
...." cellspacing="0" width="920" height="547"><tr><
âœ‰

Error Line 1 column 652: end tag for "SPAN" omitted, but its declaration
does not permit this.
....p; SEARCH ENGINES SEAR</font></b></td><td></td><td
height="14"></td></tr><tr>
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.

âœ‰

Info Line 1 column 405: start tag was here.
....le="margin-top: 0; margin-bottom: 0"><span style="font-family: verdana;
font-
Error Line 1 column 1310: document type does not allow element "P" here;
missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
....: 0; margin-bottom: 0" align="center">Please stick around and find out
for yo
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>").

âœ‰

Error Line 1 column 1409: there is no attribute "FACE".
....href="advantage%20of%20sel.htm" face="Verdana" style="font-size: 12px;
font-w
âœ‰

Error Line 1 column 1488: there is no attribute "COLOR".
....ght:700; text-decoration:none" color="#BF540D"><font
color="#BF540D">advantag
âœ‰

Error Line 1 column 1626: end tag for "FONT" omitted, but its declaration
does not permit this.
....n just Goggle & Yahoo. </td></tr></table></td></tr></table></td><td
âœ‰

Info Line 1 column 1152: start tag was here.
.... 0; margin-bottom: 0" align="center"><font face="Verdana"
style="font-size: 1
Error Line 1 column 1779: required attribute "ALT" not specified.
....elocator.gif" width="399" height="61"></span></td><td valign="middle"
colspan
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>.

âœ‰

Error Line 1 column 1786: end tag for element "SPAN" which is not open.
....r.gif" width="399" height="61"></span></td><td valign="middle"
colspan="3" ro
The Validator found an end tag for the above element, but that element is
not currently open. This is often caused by a leftover end tag from an
element that was removed during editing, or by an implicitly closed element
(if you have an error related to an element being used where it is not
allowed, this is almost certainly the case). In the latter case this error
will disappear as soon as you fix the original problem.

If this error occured in a script section of your document, you should
probably read this FAQ entry.

âœ‰

Error Line 1 column 2258: "FONT-FAMILY:" is not a member of a group
specified for any attribute.
....margin-bottom: 0"><span FONT-FAMILY: verdana"><font color="#000066"><span
sty
âœ‰

Error Line 1 column 2265: an attribute value literal can occur in an
attribute specification list only after a VI delimiter.
....bottom: 0"><span FONT-FAMILY: verdana"><font color="#000066"><span
style="tex
Have you forgotten the "equal" sign marking the separation between the
attribute and its declared value? Typical syntax is attribute="value".

âœ‰

Error Line 1 column 3002: document type does not allow element "P" here;
missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
....: 0; margin-bottom: 0" align="center">My apology, Search Engine Locator
is st
âœ‰

Error Line 1 column 3119: document type does not allow element "P" here;
missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
....: 0; margin-bottom: 0" align="center">Here I'll keep you inform what is
avail
âœ‰

Error Line 1 column 3239: document type does not allow element "P" here;
missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
....: 0; margin-bottom: 0" align="center">"By Alphabet"</p><p style="ma
âœ‰

Error Line 1 column 3309: document type does not allow element "P" here;
missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
....yle="margin-top: 0; margin-bottom: 0"> </p></td></tr></table></td></tr><
âœ‰

Error Line 1 column 3324: end tag for "FONT" omitted, but its declaration
does not permit this.
....: 0; margin-bottom: 0"> </p></td></tr></table></td></tr></table></td><td
âœ‰

Info Line 1 column 2884: start tag was here.
...."100%" height="100%" valign="middle"><font face="Verdana"
style="font-size: 1
Error Line 1 column 3734: end tag for "FONT" omitted, but its declaration
does not permit this.
....chenginelocator.com</span></font></td><td></td><td
height="22"></td></tr><tr>
âœ‰

Info Line 1 column 3555: start tag was here.
....size:9 px; font-family:Verdana; px" ><font
color="#000066">SearchEngineLocato
Error Line 1 column 3734: end tag for "SPAN" omitted, but its declaration
does not permit this.
....chenginelocator.com</span></font></td><td></td><td
height="22"></td></tr><tr>
âœ‰

Info Line 1 column 3477: start tag was here.
.... bgcolor="#FFE88A"><p align="center"><span style="text-decoration: none;
font
Error Line 1 column 4328: end tag for "FONT" omitted, but its declaration
does not permit this.
....S & DIRECTORIES</span></font></span></td></tr></table><td></t
âœ‰

Info Line 1 column 4190: start tag was here.
....amily: verdana; font-size: 14px;"><b><font face= "Verdana"
color="#BF540D">A&
Error Line 1 column 4328: end tag for "B" omitted, but its declaration does
not permit this.
....S & DIRECTORIES</span></font></span></td></tr></table><td></t
âœ‰

Info Line 1 column 4187: start tag was here.
....t-family: verdana; font-size: 14px;"><b><font face= "Verdana"
color="#BF540D"
Error Line 1 column 4335: end tag for "B" omitted, but its declaration does
not permit this.
.... & DIRECTORIES</span></font></span></td></tr></table><td></td><td h
âœ‰

Info Line 1 column 4131: start tag was here.
....gin-bottom: 0"><font color="#FFCC00"><b><span style="font-family:
verdana; fo
Error Line 1

Murray · Dec 12, 2005

Just post a link to the page, please.

Vanilla · Dec 12, 2005

http://www.w3schools.com/site/site_validate.asp
Thanks

Murray · Dec 13, 2005

Uhhh - post a link to YOUR pge - the one that is giving you problems....

Vanilla · Dec 13, 2005

http://www.searchenginelocator.com

Stefan B Rusynko · Dec 13, 2005

Vanilla · Dec 14, 2005

I appriciate your concern. I've had the validation test and failed again.
Every time I fail, I get more errors. Now I am up to 184.
I'm sure that somebody has the answer out there. I appriciate any thoguths
on this subject.
Thank you
Vanilla, http://www.searchenginelocator.com
Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
"From one small seed of kindness ... friendship grows."

Stefan B Rusynko said:
Start in code view and add the doc type per Murray's instructions
Check your pages using Tools Browser Compatibility
Then Turn off the Optimize html options and republish your site

PS
you will never get a complete validation as long as you are using FP design time webbots
- but the errors you get from them will not prevent the pages from being correct

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________

| http://www.searchenginelocator.com
| --
| Vanilla
| Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| http://www.searchenginelocator.com
| "From one small seed of kindness ... friendship grows."
|
|
| "Murray" wrote:
|
| > Uhhh - post a link to YOUR pge - the one that is giving you problems....
| >
| > --
| > Murray
| > ============
| >
| > | > >
| > > http://www.w3schools.com/site/site_validate.asp
| > > Thanks
| > >
| > > --
| > > Vanilla
| > > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > > http://www.searchenginelocator.com
| > > "From one small seed of kindness ... friendship grows."
| > >
| > >
| > > "Murray" wrote:
| > >
| > >> Just post a link to the page, please.
| > >>
| > >> --
| > >> Murray
| > >> ============
| > >>
| > >> | > >> >I thought that I followed your instructions, but probably I'm doing
| > >> >something
| > >> > wrong, because I am back to 182 errors! Here is the result. I
| > >> > appriciate
| > >> > your help.
| > >> > Result--just part of it--: Failed validation, 182 errors
| > >> > Address:
| > >> > Encoding: iso-8859-1 (detect automatically) utf-8 (Unicode, worldwide)
| > >> > utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2
| > >> > (Central
| > >> > Europe) iso-8859-3 (Southern Europe) iso-8859-4 (Baltic Rim) iso-8859-5
| > >> > (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8-i
| > >> > (Hebrew)
| > >> > iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-13 (Latin 7)
| > >> > iso-8859-14
| > >> > (Celtic) iso-8859-15 (Latin 9) us-ascii (basic English) euc-jp
| > >> > (Japanese,
| > >> > Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email)
| > >> > euc-kr
| > >> > (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified)
| > >> > big5
| > >> > (Chinese, traditional) tis-620 (Thai) koi8-r (Russian) koi8-u
| > >> > (Ukrainian)
| > >> > macintosh (MacRoman) windows-1250 (Central Europe) windows-1251
| > >> > (Cyrillic)
| > >> > windows-1252 (Western Europe) windows-1253 (Greek) windows-1254
| > >> > (Turkish)
| > >> > windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)
| > >> > Doctype: (no Doctype found) (detect automatically) XHTML 1.1 XHTML
| > >> > Basic
| > >> > 1.0 XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset ISO/IEC
| > >> > 15445:2000 ("ISO HTML") HTML 4.01 Strict HTML 4.01 Transitional HTML
| > >> > 4.01
| > >> > Frameset HTML 3.2 HTML 2.0 MathML 2.0 XHTML 1.1 plus MathML 2.0
| > >> > Revalidate With Options: Show Source Show Outline
| > >> > Show Parse Tree ...no attributes
| > >> > Validate error pages Verbose Output
| > >> >
| > >> > Help on the options is available.
| > >> >
| > >> > No DOCTYPE found! Attempting validation with HTML 4.01 Transitional.
| > >> > The
| > >> > DOCTYPE Declaration was not recognized or is missing. This probably
| > >> > means
| > >> > that the Formal Public Identifier contains a spelling error, or that
| > >> > the
| > >> > Declaration is not using correct syntax. Validation has been performed
| > >> > using
| > >> > a default "fallback" Document Type Definition that closely resembles
| > >> > "HTML
| > >> > 4.01 Transitional", but the document will not be Valid until you have
| > >> > corrected this problem with the DOCTYPE Declaration.
| > >> >
| > >> > Learn how to add a doctype to your document from our FAQ.
| > >> >
| > >> > This page is not Valid (no Doctype found)!
| > >> > Below are the results of attempting to parse this document with an SGML
| > >> > parser.
| > >> >
| > >> > Error Line 1 column 0: no document type declaration; implying
| > >> > "<!DOCTYPE
| > >> > HTML SYSTEM>".
| > >> > <html><head><meta http-equiv="Content-Type" content="text/html;
| > >> > charset=iso-8859
| > >> > The checked page did not contain a document type ("DOCTYPE")
| > >> > declaration.
| > >> > The Validator has tried to validate with a fallback DTD, but this is
| > >> > quite
| > >> > likely to be incorrect and will generate a large number of incorrect
| > >> > error
| > >> > messages. It is highly recommended that you insert the proper DOCTYPE
| > >> > declaration in your document -- instructions for doing this are given
| > >> > above
| > >> > -- and it is necessary to have this declaration before the page can be
| > >> > declared to be valid.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 216: there is no attribute "TOPMARGIN".
| > >> > ...ad><body bgcolor="#E6E6FF" topmargin="00"><table cellpadding="0"
| > >> > cellspacing=
| > >> > 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.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 279: there is no attribute "HEIGHT".
| > >> > ..." cellspacing="0" width="920" height="547"><tr><
| > >> > ?
| > >> >
| > >> > Error Line 1 column 652: end tag for "SPAN" omitted, but its
| > >> > declaration
| > >> > does not permit this.
| > >> > ...p; SEARCH ENGINES SEAR</font></b></td><td></td><td
| > >> > height="14"></td></tr><tr>
| > >> > 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.
| > >> >
| > >> > ?
| > >> >
| > >> > Info Line 1 column 405: start tag was here.
| > >> > ...le="margin-top: 0; margin-bottom: 0"><span style="font-family:
| > >> > verdana;
| > >> > font-
| > >> > Error Line 1 column 1310: document type does not allow element "P"
| > >> > here;
| > >> > missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
| > >> > ...: 0; margin-bottom: 0" align="center">Please stick around and find
| > >> > out
| > >> > for yo
| > >> > 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>").
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 1409: there is no attribute "FACE".
| > >> > ...href="advantage%20of%20sel.htm" face="Verdana" style="font-size:
| > >> > 12px;
| > >> > font-w
| > >> > ?
| > >> >
| > >> > Error Line 1 column 1488: there is no attribute "COLOR".
| > >> > ...ght:700; text-decoration:none" color="#BF540D"><font
| > >> > color="#BF540D">advantag
| > >> > ?
| > >> >
| > >> > Error Line 1 column 1626: end tag for "FONT" omitted, but its
| > >> > declaration
| > >> > does not permit this.
| > >> > ...n just Goggle & Yahoo. </td></tr></table></td></tr></table></td><td
| > >> > ?
| > >> >
| > >> > Info Line 1 column 1152: start tag was here.
| > >> > ... 0; margin-bottom: 0" align="center"><font face="Verdana"
| > >> > style="font-size: 1
| > >> > Error Line 1 column 1779: required attribute "ALT" not specified.
| > >> > ...elocator.gif" width="399" height="61"></span></td><td
| > >> > valign="middle"
| > >> > colspan
| > >> > 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>.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 1786: end tag for element "SPAN" which is not open.
| > >> > ...r.gif" width="399" height="61"></span></td><td valign="middle"
| > >> > colspan="3" ro
| > >> > The Validator found an end tag for the above element, but that element
| > >> > is
| > >> > not currently open. This is often caused by a leftover end tag from an
| > >> > element that was removed during editing, or by an implicitly closed
| > >> > element
| > >> > (if you have an error related to an element being used where it is not
| > >> > allowed, this is almost certainly the case). In the latter case this
| > >> > error
| > >> > will disappear as soon as you fix the original problem.
| > >> >
| > >> > If this error occured in a script section of your document, you should
| > >> > probably read this FAQ entry.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 2258: "FONT-FAMILY:" is not a member of a group
| > >> > specified for any attribute.
| > >> > ...margin-bottom: 0"><span FONT-FAMILY: verdana"><font
| > >> > color="#000066"><span
| > >> > sty
| > >> > ?
| > >> >
| > >> > Error Line 1 column 2265: an attribute value literal can occur in an
| > >> > attribute specification list only after a VI delimiter.
| > >> > ...bottom: 0"><span FONT-FAMILY: verdana"><font color="#000066"><span
| > >> > style="tex
| > >> > Have you forgotten the "equal" sign marking the separation between the
| > >> > attribute and its declared value? Typical syntax is attribute="value".
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 3002: document type does not allow element "P"
| > >> > here;
| > >> > missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
| > >> > ...: 0; margin-bottom: 0" align="center">My apology, Search Engine
| > >> > Locator
| > >> > is st
| > >> > ?

Ronx · Dec 14, 2005

First, open the web and then the page in FrontPage.
Got to Code view
Change
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.searchenginelcoator.com"><meta
http-equiv="Content-Type" content="text/html;
charset=iso-8859-1"><html><head><meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
to
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">

Then right click anywhere in the code and choose Reformat HTML.
When you republish the page, before hitting the publish button, click
on Optimise Published HTML... and clear ALL the check boxes.

Then publish and try the validation check.
Your page currently has all white space removed, which makes it
impossible to see what is going on.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/

Vanilla said:
I appriciate your concern. I've had the validation test and failed again.
Every time I fail, I get more errors. Now I am up to 184.
I'm sure that somebody has the answer out there. I appriciate any thoguths
on this subject.
Thank you
Vanilla, http://www.searchenginelocator.com
Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
"From one small seed of kindness ... friendship grows."

Stefan B Rusynko said:

Start in code view and add the doc type per Murray's instructions
Check your pages using Tools Browser Compatibility
Then Turn off the Optimize html options and republish your site

PS
you will never get a complete validation as long as you are using FP design time webbots
- but the errors you get from them will not prevent the pages from being correct

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________

| http://www.searchenginelocator.com
| --
| Vanilla
| Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| http://www.searchenginelocator.com
| "From one small seed of kindness ... friendship grows."
|
|
| "Murray" wrote:
|
| > Uhhh - post a link to YOUR pge - the one that is giving you problems....
| >
| > --
| > Murray
| > ============
| >
| > | > >
| > > http://www.w3schools.com/site/site_validate.asp
| > > Thanks
| > >
| > > --
| > > Vanilla
| > > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > > http://www.searchenginelocator.com
| > > "From one small seed of kindness ... friendship grows."
| > >
| > >
| > > "Murray" wrote:
| > >
| > >> Just post a link to the page, please.
| > >>
| > >> --
| > >> Murray
| > >> ============
| > >>
| > >> | > >> >I thought that I followed your instructions, but probably I'm doing
| > >> >something
| > >> > wrong, because I am back to 182 errors! Here is the result. I
| > >> > appriciate
| > >> > your help.
| > >> > Result--just part of it--: Failed validation, 182 errors
| > >> > Address:
| > >> > Encoding: iso-8859-1 (detect automatically) utf-8 (Unicode, worldwide)
| > >> > utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2
| > >> > (Central
| > >> > Europe) iso-8859-3 (Southern Europe) iso-8859-4 (Baltic Rim) iso-8859-5
| > >> > (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8-i
| > >> > (Hebrew)
| > >> > iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-13 (Latin 7)
| > >> > iso-8859-14
| > >> > (Celtic) iso-8859-15 (Latin 9) us-ascii (basic English) euc-jp
| > >> > (Japanese,
| > >> > Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email)
| > >> > euc-kr
| > >> > (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified)
| > >> > big5
| > >> > (Chinese, traditional) tis-620 (Thai) koi8-r (Russian) koi8-u
| > >> > (Ukrainian)
| > >> > macintosh (MacRoman) windows-1250 (Central Europe) windows-1251
| > >> > (Cyrillic)
| > >> > windows-1252 (Western Europe) windows-1253 (Greek) windows-1254
| > >> > (Turkish)
| > >> > windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)
| > >> > Doctype: (no Doctype found) (detect automatically) XHTML 1.1 XHTML
| > >> > Basic
| > >> > 1.0 XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset ISO/IEC
| > >> > 15445:2000 ("ISO HTML") HTML 4.01 Strict HTML 4.01 Transitional HTML
| > >> > 4.01
| > >> > Frameset HTML 3.2 HTML 2.0 MathML 2.0 XHTML 1.1 plus MathML 2.0
| > >> > Revalidate With Options: Show Source Show Outline
| > >> > Show Parse Tree ...no attributes
| > >> > Validate error pages Verbose Output
| > >> >
| > >> > Help on the options is available.
| > >> >
| > >> > No DOCTYPE found! Attempting validation with HTML 4.01 Transitional.
| > >> > The
| > >> > DOCTYPE Declaration was not recognized or is missing. This probably
| > >> > means
| > >> > that the Formal Public Identifier contains a spelling error, or that
| > >> > the
| > >> > Declaration is not using correct syntax. Validation has been performed
| > >> > using
| > >> > a default "fallback" Document Type Definition that closely resembles
| > >> > "HTML
| > >> > 4.01 Transitional", but the document will not be Valid until you have
| > >> > corrected this problem with the DOCTYPE Declaration.
| > >> >
| > >> > Learn how to add a doctype to your document from our FAQ.
| > >> >
| > >> > This page is not Valid (no Doctype found)!
| > >> > Below are the results of attempting to parse this document with an SGML
| > >> > parser.
| > >> >
| > >> > Error Line 1 column 0: no document type declaration; implying
| > >> > "<!DOCTYPE
| > >> > HTML SYSTEM>".
| > >> > <html><head><meta http-equiv="Content-Type" content="text/html;
| > >> > charset=iso-8859
| > >> > The checked page did not contain a document type ("DOCTYPE")
| > >> > declaration.
| > >> > The Validator has tried to validate with a fallback DTD, but this is
| > >> > quite
| > >> > likely to be incorrect and will generate a large number of incorrect
| > >> > error
| > >> > messages. It is highly recommended that you insert the proper DOCTYPE
| > >> > declaration in your document -- instructions for doing this are given
| > >> > above
| > >> > -- and it is necessary to have this declaration before the page can be
| > >> > declared to be valid.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 216: there is no attribute "TOPMARGIN".
| > >> > ...ad><body bgcolor="#E6E6FF" topmargin="00"><table cellpadding="0"
| > >> > cellspacing=
| > >> > 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.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 279: there is no attribute "HEIGHT".
| > >> > ..." cellspacing="0" width="920" height="547"><tr><
| > >> > ?
| > >> >
| > >> > Error Line 1 column 652: end tag for "SPAN" omitted, but its
| > >> > declaration
| > >> > does not permit this.
| > >> > ...p; SEARCH ENGINES SEAR</font></b></td><td></td><td
| > >> > height="14"></td></tr><tr>
| > >> > 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.
| > >> >
| > >> > ?
| > >> >
| > >> > Info Line 1 column 405: start tag was here.
| > >> > ...le="margin-top: 0; margin-bottom: 0"><span style="font-family:
| > >> > verdana;
| > >> > font-
| > >> > Error Line 1 column 1310: document type does not allow element "P"
| > >> > here;
| > >> > missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
| > >> > ...: 0; margin-bottom: 0" align="center">Please stick around and find
| > >> > out
| > >> > for yo
| > >> > 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>").
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 1409: there is no attribute "FACE".
| > >> > ...href="advantage%20of%20sel.htm" face="Verdana" style="font-size:
| > >> > 12px;
| > >> > font-w
| > >> > ?
| > >> >
| > >> > Error Line 1 column 1488: there is no attribute "COLOR".
| > >> > ...ght:700; text-decoration:none" color="#BF540D"><font
| > >> > color="#BF540D">advantag
| > >> > ?
| > >> >
| > >> > Error Line 1 column 1626: end tag for "FONT" omitted, but its
| > >> > declaration
| > >> > does not permit this.
| > >> > ...n just Goggle & Yahoo.

Click to expand...

| > >> > ?
| > >> >
| > >> > Info Line 1 column 1152: start tag was here.
| > >> > ... 0; margin-bottom: 0" align="center"><font face="Verdana"
| > >> > style="font-size: 1
| > >> > Error Line 1 column 1779: required attribute "ALT" not specified.
| > >> > ...elocator.gif" width="399" height="61"></span></td><td
| > >> > valign="middle"
| > >> > colspan
| > >> > 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>.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 1786: end tag for element "SPAN" which is not open.
| > >> > ...r.gif" width="399" height="61"></span></td><td valign="middle"
| > >> > colspan="3" ro
| > >> > The Validator found an end tag for the above element, but that element
| > >> > is
| > >> > not currently open. This is often caused by a leftover end tag from an
| > >> > element that was removed during editing, or by an implicitly closed
| > >> > element
| > >> > (if you have an error related to an element being used where it is not
| > >> > allowed, this is almost certainly the case). In the latter case this
| > >> > error
| > >> > will disappear as soon as you fix the original problem.
| > >> >
| > >> > If this error occured in a script section of your document, you should
| > >> > probably read this FAQ entry.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 2258: "FONT-FAMILY:" is not a member of a group
| > >> > specified for any attribute.
| > >> > ...margin-bottom: 0"><span FONT-FAMILY: verdana"><font
| > >> > color="#000066"><span
| > >> > sty
| > >> > ?
| > >> >
| > >> > Error Line 1 column 2265: an attribute value literal can occur in an
| > >> > attribute specification list only after a VI delimiter.
| > >> > ...bottom: 0"><span FONT-FAMILY: verdana"><font color="#000066"><span
| > >> > style="tex
| > >> > Have you forgotten the "equal" sign marking the separation between the
| > >> > attribute and its declared value? Typical syntax is attribute="value".
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 3002: document type does not allow element "P"
| > >> > here;
| > >> > missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
| > >> > ...: 0; margin-bottom: 0" align="center">My apology, Search Engine
| > >> > Locator
| > >> > is st
| > >> > ?

Click to expand...

Vanilla · Dec 16, 2005

I did what Ronx suggested (thanks) but it did not changeâ€”or I did not realize
that it did as the numbers of errors were the same--my error report.
Right now Iâ€™m working on my webpage using the validation test. 184 errors
are down to 124.
I try to make sense of the explanations that follow every error. There are
things (a lot) that I could not figure out myself & need some help with it.
1.) â€œThis page is not Valid HTML 4.01 Transitional! Below are the results
of attempting to parse this document with an SGML parser.â€

I thought that FrontPage is using HTML.

2.)Every error is identified by their â€˜where-aboutsâ€™: x line y column. My
question is that what the â€˜columnâ€™ is referring to?

3.) â€œLine 8 column 23: document type does not allow element "BODY" here.
<body bgcolor="#E6E6FF">â€

It was created by Frontpage 2003 while I used WYSIWYG option.
I deleted it but it appeared again when I defined the page colour.

Thanks guys & galls for all your helps.

--
Vanilla
Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
http://www.searchenginelocator.com
"From one small seed of kindness ... friendship grows."

Ronx said:
First, open the web and then the page in FrontPage.
Got to Code view
Change
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.searchenginelcoator.com"><meta
http-equiv="Content-Type" content="text/html;
charset=iso-8859-1"><html><head><meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
to
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">

Then right click anywhere in the code and choose Reformat HTML.
When you republish the page, before hitting the publish button, click
on Optimise Published HTML... and clear ALL the check boxes.

Then publish and try the validation check.
Your page currently has all white space removed, which makes it
impossible to see what is going on.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/

Vanilla said:

I appriciate your concern. I've had the validation test and failed again.
Every time I fail, I get more errors. Now I am up to 184.
I'm sure that somebody has the answer out there. I appriciate any thoguths
on this subject.
Thank you
Vanilla, http://www.searchenginelocator.com
Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
"From one small seed of kindness ... friendship grows."

Stefan B Rusynko said:

Start in code view and add the doc type per Murray's instructions
Check your pages using Tools Browser Compatibility
Then Turn off the Optimize html options and republish your site

PS
you will never get a complete validation as long as you are using FP design time webbots
- but the errors you get from them will not prevent the pages from being correct

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________

| http://www.searchenginelocator.com
| --
| Vanilla
| Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| http://www.searchenginelocator.com
| "From one small seed of kindness ... friendship grows."
|
|
| "Murray" wrote:
|
| > Uhhh - post a link to YOUR pge - the one that is giving you problems....
| >
| > --
| > Murray
| > ============
| >
| > | > >
| > > http://www.w3schools.com/site/site_validate.asp
| > > Thanks
| > >
| > > --
| > > Vanilla
| > > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > > http://www.searchenginelocator.com
| > > "From one small seed of kindness ... friendship grows."
| > >
| > >
| > > "Murray" wrote:
| > >
| > >> Just post a link to the page, please.
| > >>
| > >> --
| > >> Murray
| > >> ============
| > >>
| > >> | > >> >I thought that I followed your instructions, but probably I'm doing
| > >> >something
| > >> > wrong, because I am back to 182 errors! Here is the result. I
| > >> > appriciate
| > >> > your help.
| > >> > Result--just part of it--: Failed validation, 182 errors
| > >> > Address:
| > >> > Encoding: iso-8859-1 (detect automatically) utf-8 (Unicode, worldwide)
| > >> > utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2
| > >> > (Central
| > >> > Europe) iso-8859-3 (Southern Europe) iso-8859-4 (Baltic Rim) iso-8859-5
| > >> > (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8-i
| > >> > (Hebrew)
| > >> > iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-13 (Latin 7)
| > >> > iso-8859-14
| > >> > (Celtic) iso-8859-15 (Latin 9) us-ascii (basic English) euc-jp
| > >> > (Japanese,
| > >> > Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email)
| > >> > euc-kr
| > >> > (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified)
| > >> > big5
| > >> > (Chinese, traditional) tis-620 (Thai) koi8-r (Russian) koi8-u
| > >> > (Ukrainian)
| > >> > macintosh (MacRoman) windows-1250 (Central Europe) windows-1251
| > >> > (Cyrillic)
| > >> > windows-1252 (Western Europe) windows-1253 (Greek) windows-1254
| > >> > (Turkish)
| > >> > windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)
| > >> > Doctype: (no Doctype found) (detect automatically) XHTML 1.1 XHTML
| > >> > Basic
| > >> > 1.0 XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset ISO/IEC
| > >> > 15445:2000 ("ISO HTML") HTML 4.01 Strict HTML 4.01 Transitional HTML
| > >> > 4.01
| > >> > Frameset HTML 3.2 HTML 2.0 MathML 2.0 XHTML 1.1 plus MathML 2.0
| > >> > Revalidate With Options: Show Source Show Outline
| > >> > Show Parse Tree ...no attributes
| > >> > Validate error pages Verbose Output
| > >> >
| > >> > Help on the options is available.
| > >> >
| > >> > No DOCTYPE found! Attempting validation with HTML 4.01 Transitional.
| > >> > The
| > >> > DOCTYPE Declaration was not recognized or is missing. This probably
| > >> > means
| > >> > that the Formal Public Identifier contains a spelling error, or that
| > >> > the
| > >> > Declaration is not using correct syntax. Validation has been performed
| > >> > using
| > >> > a default "fallback" Document Type Definition that closely resembles
| > >> > "HTML
| > >> > 4.01 Transitional", but the document will not be Valid until you have
| > >> > corrected this problem with the DOCTYPE Declaration.
| > >> >
| > >> > Learn how to add a doctype to your document from our FAQ.
| > >> >
| > >> > This page is not Valid (no Doctype found)!
| > >> > Below are the results of attempting to parse this document with an SGML
| > >> > parser.
| > >> >
| > >> > Error Line 1 column 0: no document type declaration; implying
| > >> > "<!DOCTYPE
| > >> > HTML SYSTEM>".
| > >> > <html><head><meta http-equiv="Content-Type" content="text/html;
| > >> > charset=iso-8859
| > >> > The checked page did not contain a document type ("DOCTYPE")
| > >> > declaration.
| > >> > The Validator has tried to validate with a fallback DTD, but this is
| > >> > quite
| > >> > likely to be incorrect and will generate a large number of incorrect
| > >> > error
| > >> > messages. It is highly recommended that you insert the proper DOCTYPE
| > >> > declaration in your document -- instructions for doing this are given
| > >> > above
| > >> > -- and it is necessary to have this declaration before the page can be
| > >> > declared to be valid.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 216: there is no attribute "TOPMARGIN".
| > >> > ...ad><body bgcolor="#E6E6FF" topmargin="00"><table cellpadding="0"
| > >> > cellspacing=
| > >> > 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.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 279: there is no attribute "HEIGHT".
| > >> > ..." cellspacing="0" width="920" height="547"><tr><
| > >> > ?
| > >> >
| > >> > Error Line 1 column 652: end tag for "SPAN" omitted, but its
| > >> > declaration
| > >> > does not permit this.
| > >> > ...p; SEARCH ENGINES SEAR</font></b></td><td></td><td
| > >> > height="14"></td></tr><tr>
| > >> > 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.
| > >> >
| > >> > ?
| > >> >
| > >> > Info Line 1 column 405: start tag was here.
| > >> > ...le="margin-top: 0; margin-bottom: 0"><span

Click to expand...

Click to expand...

style="font-family:

Murray · Dec 16, 2005

I thought that FrontPage is using HTML.

It is. The error probably means that the page doesn't have a valid and
complete doctype.

2.)Every error is identified by their 'where-abouts': x line y column. My
question is that what the 'column' is referring to?

Ignore it, usually. Sometimes it would be the number of characters to the
right of the left margin.

3.) "Line 8 column 23: document type does not allow element "BODY" here.
<body bgcolor="#E6E6FF">"

I would have to see the page to tell you why this is.

--
Murray
============

Vanilla said:
I did what Ronx suggested (thanks) but it did not change-or I did not
realize
that it did as the numbers of errors were the same--my error report.
Right now I'm working on my webpage using the validation test. 184 errors
are down to 124.
I try to make sense of the explanations that follow every error. There
are
things (a lot) that I could not figure out myself & need some help with
it.
1.) "This page is not Valid HTML 4.01 Transitional! Below are the results
of attempting to parse this document with an SGML parser."

I thought that FrontPage is using HTML.

2.)Every error is identified by their 'where-abouts': x line y column. My
question is that what the 'column' is referring to?

3.) "Line 8 column 23: document type does not allow element "BODY" here.
<body bgcolor="#E6E6FF">"

It was created by Frontpage 2003 while I used WYSIWYG option.
I deleted it but it appeared again when I defined the page colour.

Thanks guys & galls for all your helps.

--
Vanilla
Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
http://www.searchenginelocator.com
"From one small seed of kindness ... friendship grows."

Ronx said:

First, open the web and then the page in FrontPage.
Got to Code view
Change
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.searchenginelcoator.com"><meta
http-equiv="Content-Type" content="text/html;
charset=iso-8859-1"><html><head><meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
to
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">

Then right click anywhere in the code and choose Reformat HTML.
When you republish the page, before hitting the publish button, click
on Optimise Published HTML... and clear ALL the check boxes.

Then publish and try the validation check.
Your page currently has all white space removed, which makes it
impossible to see what is going on.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/

Vanilla said:

I appriciate your concern. I've had the validation test and failed again.
Every time I fail, I get more errors. Now I am up to 184.
I'm sure that somebody has the answer out there. I appriciate any thoguths
on this subject.
Thank you
Vanilla, http://www.searchenginelocator.com
Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
"From one small seed of kindness ... friendship grows."

:

Start in code view and add the doc type per Murray's instructions
Check your pages using Tools Browser Compatibility
Then Turn off the Optimize html options and republish your site

PS
you will never get a complete validation as long as you are using FP design time webbots
- but the errors you get from them will not prevent the pages from being correct

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________

| http://www.searchenginelocator.com
| --
| Vanilla
| Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| http://www.searchenginelocator.com
| "From one small seed of kindness ... friendship grows."
|
|
| "Murray" wrote:
|
| > Uhhh - post a link to YOUR pge - the one that is giving you problems....
| >
| > --
| > Murray
| > ============
| >
| > | > >
| > > http://www.w3schools.com/site/site_validate.asp
| > > Thanks
| > >
| > > --
| > > Vanilla
| > > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > > http://www.searchenginelocator.com
| > > "From one small seed of kindness ... friendship grows."
| > >
| > >
| > > "Murray" wrote:
| > >
| > >> Just post a link to the page, please.
| > >>
| > >> --
| > >> Murray
| > >> ============
| > >>
| > >> | > >> >I thought that I followed your instructions, but probably I'm doing
| > >> >something
| > >> > wrong, because I am back to 182 errors! Here is the result. I
| > >> > appriciate
| > >> > your help.
| > >> > Result--just part of it--: Failed validation, 182 errors
| > >> > Address:
| > >> > Encoding: iso-8859-1 (detect automatically) utf-8 (Unicode, worldwide)
| > >> > utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2
| > >> > (Central
| > >> > Europe) iso-8859-3 (Southern Europe) iso-8859-4 (Baltic Rim) iso-8859-5
| > >> > (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8-i
| > >> > (Hebrew)
| > >> > iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-13 (Latin 7)
| > >> > iso-8859-14
| > >> > (Celtic) iso-8859-15 (Latin 9) us-ascii (basic English) euc-jp
| > >> > (Japanese,
| > >> > Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email)
| > >> > euc-kr
| > >> > (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified)
| > >> > big5
| > >> > (Chinese, traditional) tis-620 (Thai) koi8-r (Russian) koi8-u
| > >> > (Ukrainian)
| > >> > macintosh (MacRoman) windows-1250 (Central Europe) windows-1251
| > >> > (Cyrillic)
| > >> > windows-1252 (Western Europe) windows-1253 (Greek) windows-1254
| > >> > (Turkish)
| > >> > windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)
| > >> > Doctype: (no Doctype found) (detect automatically) XHTML 1.1 XHTML
| > >> > Basic
| > >> > 1.0 XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset ISO/IEC
| > >> > 15445:2000 ("ISO HTML") HTML 4.01 Strict HTML 4.01 Transitional HTML
| > >> > 4.01
| > >> > Frameset HTML 3.2 HTML 2.0 MathML 2.0 XHTML 1.1 plus MathML 2.0
| > >> > Revalidate With Options: Show Source Show Outline
| > >> > Show Parse Tree ...no attributes
| > >> > Validate error pages Verbose Output
| > >> >
| > >> > Help on the options is available.
| > >> >
| > >> > No DOCTYPE found! Attempting validation with HTML 4.01 Transitional.
| > >> > The
| > >> > DOCTYPE Declaration was not recognized or is missing. This probably
| > >> > means
| > >> > that the Formal Public Identifier contains a spelling error, or that
| > >> > the
| > >> > Declaration is not using correct syntax. Validation has been performed
| > >> > using
| > >> > a default "fallback" Document Type Definition that closely resembles
| > >> > "HTML
| > >> > 4.01 Transitional", but the document will not be Valid until you have
| > >> > corrected this problem with the DOCTYPE Declaration.
| > >> >
| > >> > Learn how to add a doctype to your document from our FAQ.
| > >> >
| > >> > This page is not Valid (no Doctype found)!
| > >> > Below are the results of attempting to parse this document with an SGML
| > >> > parser.
| > >> >
| > >> > Error Line 1 column 0: no document type declaration; implying
| > >> > "<!DOCTYPE
| > >> > HTML SYSTEM>".
| > >> > <html><head><meta http-equiv="Content-Type" content="text/html;
| > >> > charset=iso-8859
| > >> > The checked page did not contain a document type ("DOCTYPE")
| > >> > declaration.
| > >> > The Validator has tried to validate with a fallback DTD, but this is
| > >> > quite
| > >> > likely to be incorrect and will generate a large number of incorrect
| > >> > error
| > >> > messages. It is highly recommended that you insert the proper DOCTYPE
| > >> > declaration in your document -- instructions for doing this are given
| > >> > above
| > >> > -- and it is necessary to have this declaration before the page can be
| > >> > declared to be valid.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 216: there is no attribute "TOPMARGIN".
| > >> > ...ad><body bgcolor="#E6E6FF" topmargin="00"><table cellpadding="0"
| > >> > cellspacing=
| > >> > 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.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 279: there is no attribute "HEIGHT".
| > >> > ..." cellspacing="0" width="920" height="547"><tr><
| > >> > ?
| > >> >
| > >> > Error Line 1 column 652: end tag for "SPAN" omitted, but its
| > >> > declaration
| > >> > does not permit this.
| > >> > ...p; SEARCH ENGINES SEAR</font></b></td><td></td><td
| > >> > height="14"></td></tr><tr>
| > >> > 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.
| > >> >
| > >> > ?
| > >> >
| > >> > Info Line 1 column 405: start tag was here.
| > >> > ...le="margin-top: 0; margin-bottom: 0"><span

Click to expand...

style="font-family:

Click to expand...

Vanilla · Dec 17, 2005

my website: http://www.searchenginelocator.com
--
Vanilla
Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
my website: http://www.searchenginelocator.com
"From one small seed of kindness ... friendship grows."

Murray said:
I thought that FrontPage is using HTML.

Click to expand...

It is. The error probably means that the page doesn't have a valid and
complete doctype.

2.)Every error is identified by their 'where-abouts': x line y column. My
question is that what the 'column' is referring to?

Click to expand...

Ignore it, usually. Sometimes it would be the number of characters to the
right of the left margin.

3.) "Line 8 column 23: document type does not allow element "BODY" here.
<body bgcolor="#E6E6FF">"

Click to expand...

I would have to see the page to tell you why this is.

--
Murray
============

Vanilla said:

I did what Ronx suggested (thanks) but it did not change-or I did not
realize
that it did as the numbers of errors were the same--my error report.
Right now I'm working on my webpage using the validation test. 184 errors
are down to 124.
I try to make sense of the explanations that follow every error. There
are
things (a lot) that I could not figure out myself & need some help with
it.
1.) "This page is not Valid HTML 4.01 Transitional! Below are the results
of attempting to parse this document with an SGML parser."

I thought that FrontPage is using HTML.

2.)Every error is identified by their 'where-abouts': x line y column. My
question is that what the 'column' is referring to?

3.) "Line 8 column 23: document type does not allow element "BODY" here.
<body bgcolor="#E6E6FF">"

It was created by Frontpage 2003 while I used WYSIWYG option.
I deleted it but it appeared again when I defined the page colour.

Thanks guys & galls for all your helps.

--
Vanilla
Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
http://www.searchenginelocator.com
"From one small seed of kindness ... friendship grows."

Ronx said:

First, open the web and then the page in FrontPage.
Got to Code view
Change
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.searchenginelcoator.com"><meta
http-equiv="Content-Type" content="text/html;
charset=iso-8859-1"><html><head><meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
to
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">

Then right click anywhere in the code and choose Reformat HTML.
When you republish the page, before hitting the publish button, click
on Optimise Published HTML... and clear ALL the check boxes.

Then publish and try the validation check.
Your page currently has all white space removed, which makes it
impossible to see what is going on.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/

I appriciate your concern. I've had the validation test and failed
again.
Every time I fail, I get more errors. Now I am up to 184.
I'm sure that somebody has the answer out there. I appriciate any
thoguths
on this subject.
Thank you
Vanilla, http://www.searchenginelocator.com
Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
"From one small seed of kindness ... friendship grows."

:

Start in code view and add the doc type per Murray's instructions
Check your pages using Tools Browser Compatibility
Then Turn off the Optimize html options and republish your site

PS
you will never get a complete validation as long as you are using
FP design time webbots
- but the errors you get from them will not prevent the pages
from being correct

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:

http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________

| http://www.searchenginelocator.com
| --
| Vanilla
| Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| http://www.searchenginelocator.com
| "From one small seed of kindness ... friendship grows."
|
|
| "Murray" wrote:
|
| > Uhhh - post a link to YOUR pge - the one that is giving you
problems....
| >
| > --
| > Murray
| > ============
| >
| > | > >
| > > http://www.w3schools.com/site/site_validate.asp
| > > Thanks
| > >
| > > --
| > > Vanilla
| > > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > > http://www.searchenginelocator.com
| > > "From one small seed of kindness ... friendship grows."
| > >
| > >
| > > "Murray" wrote:
| > >
| > >> Just post a link to the page, please.
| > >>
| > >> --
| > >> Murray
| > >> ============
| > >>
message
| > >> | > >> >I thought that I followed your instructions, but probably
I'm doing
| > >> >something
| > >> > wrong, because I am back to 182 errors! Here is the
result. I
| > >> > appriciate
| > >> > your help.
| > >> > Result--just part of it--: Failed validation, 182 errors
| > >> > Address:
| > >> > Encoding: iso-8859-1 (detect automatically) utf-8
(Unicode, worldwide)
| > >> > utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe)
iso-8859-2
| > >> > (Central
| > >> > Europe) iso-8859-3 (Southern Europe) iso-8859-4 (Baltic
Rim) iso-8859-5
| > >> > (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek)
iso-8859-8-i
| > >> > (Hebrew)
| > >> > iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-13
(Latin 7)
| > >> > iso-8859-14
| > >> > (Celtic) iso-8859-15 (Latin 9) us-ascii (basic English)
euc-jp
| > >> > (Japanese,
| > >> > Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp
(Japanese, email)
| > >> > euc-kr
| > >> > (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese,
simplified)
| > >> > big5
| > >> > (Chinese, traditional) tis-620 (Thai) koi8-r (Russian)
koi8-u
| > >> > (Ukrainian)
| > >> > macintosh (MacRoman) windows-1250 (Central Europe)
windows-1251
| > >> > (Cyrillic)
| > >> > windows-1252 (Western Europe) windows-1253 (Greek)
windows-1254
| > >> > (Turkish)
| > >> > windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257
(Baltic Rim)
| > >> > Doctype: (no Doctype found) (detect automatically) XHTML
1.1 XHTML
| > >> > Basic
| > >> > 1.0 XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0
Frameset ISO/IEC
| > >> > 15445:2000 ("ISO HTML") HTML 4.01 Strict HTML 4.01
Transitional HTML
| > >> > 4.01
| > >> > Frameset HTML 3.2 HTML 2.0 MathML 2.0 XHTML 1.1 plus
MathML 2.0
| > >> > Revalidate With Options: Show Source Show Outline
| > >> > Show Parse Tree ...no attributes
| > >> > Validate error pages Verbose Output
| > >> >
| > >> > Help on the options is available.
| > >> >
| > >> > No DOCTYPE found! Attempting validation with HTML 4.01
Transitional.
| > >> > The
| > >> > DOCTYPE Declaration was not recognized or is missing.
This probably
| > >> > means
| > >> > that the Formal Public Identifier contains a spelling
error, or that
| > >> > the
| > >> > Declaration is not using correct syntax. Validation has
been performed
| > >> > using
| > >> > a default "fallback" Document Type Definition that
closely resembles
| > >> > "HTML
| > >> > 4.01 Transitional", but the document will not be Valid
until you have
| > >> > corrected this problem with the DOCTYPE Declaration.
| > >> >
| > >> > Learn how to add a doctype to your document from our FAQ.
| > >> >
| > >> > This page is not Valid (no Doctype found)!
| > >> > Below are the results of attempting to parse this
document with an SGML
| > >> > parser.
| > >> >
| > >> > Error Line 1 column 0: no document type declaration;
implying
| > >> > "<!DOCTYPE
| > >> > HTML SYSTEM>".
| > >> > <html><head><meta http-equiv="Content-Type"
content="text/html;
| > >> > charset=iso-8859
| > >> > The checked page did not contain a document type
("DOCTYPE")
| > >> > declaration.
| > >> > The Validator has tried to validate with a fallback DTD,
but this is
| > >> > quite
| > >> > likely to be incorrect and will generate a large number
of incorrect
| > >> > error
| > >> > messages. It is highly recommended that you insert the
proper DOCTYPE
| > >> > declaration in your document -- instructions for doing
this are given
| > >> > above
| > >> > -- and it is necessary to have this declaration before
the page can be
| > >> > declared to be valid.
| > >> >
| > >> > ?
| > >> >
| > >> > Error Line 1 column 216: there is no attribute
"TOPMARGIN".
| > >> > ...ad><body bgcolor="#E6E6FF" topmargin="00"><table
cellpadding="0"
| > >> > cellspacing=
| > >> > 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

Click to expand...

Click to expand...

Bob · Dec 17, 2005

A quick glance netted this....

Missing is <head> (After the <HTML> tag and </head> (before the <Body> tag

This is why the <body> tag is in the wrong place.

Also---
<body bgcolor="#E6E6FF">
<bgcolor="#E6E6FF">
you only need to declare the color once...

This will give you a start....

HTH

Bob
| my website: http://www.searchenginelocator.com
| --
| Vanilla
| Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| my website: http://www.searchenginelocator.com
| "From one small seed of kindness ... friendship grows."
|
|
| "Murray" wrote:
|
| > > I thought that FrontPage is using HTML.
| >
| > It is. The error probably means that the page doesn't have a valid and
| > complete doctype.
| >
| > > 2.)Every error is identified by their 'where-abouts': x line y column.
My
| > > question is that what the 'column' is referring to?
| >
| > Ignore it, usually. Sometimes it would be the number of characters to
the
| > right of the left margin.
| >
| > > 3.) "Line 8 column 23: document type does not allow element "BODY"
here.
| > > <body bgcolor="#E6E6FF">"
| >
| > I would have to see the page to tell you why this is.
| >
| > --
| > Murray
| > ============
| >
| > | > >I did what Ronx suggested (thanks) but it did not change-or I did not
| > >realize
| > > that it did as the numbers of errors were the same--my error report.
| > > Right now I'm working on my webpage using the validation test. 184
errors
| > > are down to 124.
| > > I try to make sense of the explanations that follow every error.
There
| > > are
| > > things (a lot) that I could not figure out myself & need some help
with
| > > it.
| > > 1.) "This page is not Valid HTML 4.01 Transitional! Below are the
results
| > > of attempting to parse this document with an SGML parser."
| > >
| > > I thought that FrontPage is using HTML.
| > >
| > > 2.)Every error is identified by their 'where-abouts': x line y column.
My
| > > question is that what the 'column' is referring to?
| > >
| > > 3.) "Line 8 column 23: document type does not allow element "BODY"
here.
| > > <body bgcolor="#E6E6FF">"
| > >
| > > It was created by Frontpage 2003 while I used WYSIWYG option.
| > > I deleted it but it appeared again when I defined the page colour.
| > >
| > >
| > > Thanks guys & galls for all your helps.
| > >
| > > --
| > > Vanilla
| > > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > > http://www.searchenginelocator.com
| > > "From one small seed of kindness ... friendship grows."
| > >
| > >
| > > "Ronx" wrote:
| > >
| > >> First, open the web and then the page in FrontPage.
| > >> Got to Code view
| > >> Change
| > >> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
| > >> "http://www.searchenginelcoator.com"><meta
| > >> http-equiv="Content-Type" content="text/html;
| > >> charset=iso-8859-1"><html><head><meta http-equiv="Content-Type"
| > >> content="text/html; charset=iso-8859-1">
| > >> to
| > >> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
| > >> "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
| > >> <html><head><meta http-equiv="Content-Type" content="text/html;
| > >> charset=iso-8859-1">
| > >>
| > >> Then right click anywhere in the code and choose Reformat HTML.
| > >> When you republish the page, before hitting the publish button, click
| > >> on Optimise Published HTML... and clear ALL the check boxes.
| > >>
| > >> Then publish and try the validation check.
| > >> Your page currently has all white space removed, which makes it
| > >> impossible to see what is going on.
| > >> --
| > >> Ron Symonds - Microsoft MVP (FrontPage)
| > >> Reply only to group - emails will be deleted unread.
| > >> FrontPage Support: http://www.frontpagemvps.com/
| > >>
| > >>
| > >> | > >> > I appriciate your concern. I've had the validation test and failed
| > >> again.
| > >> > Every time I fail, I get more errors. Now I am up to 184.
| > >> > I'm sure that somebody has the answer out there. I appriciate any
| > >> thoguths
| > >> > on this subject.
| > >> > Thank you
| > >> > Vanilla, http://www.searchenginelocator.com
| > >> > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > >> > "From one small seed of kindness ... friendship grows."
| > >> >
| > >> >
| > >> > "Stefan B Rusynko" wrote:
| > >> >
| > >> > > Start in code view and add the doc type per Murray's instructions
| > >> > > Check your pages using Tools Browser Compatibility
| > >> > > Then Turn off the Optimize html options and republish your site
| > >> > >
| > >> > > PS
| > >> > > you will never get a complete validation as long as you are using
| > >> FP design time webbots
| > >> > > - but the errors you get from them will not prevent the pages
| > >> from being correct
| > >> > >
| > >> > > --
| > >> > >
| > >> > > _____________________________________________
| > >> > > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > >> > > "Warning - Using the F1 Key will not break anything!" (-;
| > >> > > To find the best Newsgroup for FrontPage support see:
| > >> > >
| > >>
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
| > >> > > _____________________________________________
| > >> > >
| > >> > >
| > >> | > >> > > | http://www.searchenginelocator.com
| > >> > > | --
| > >> > > | Vanilla
| > >> > > | Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > >> > > | http://www.searchenginelocator.com
| > >> > > | "From one small seed of kindness ... friendship grows."
| > >> > > |
| > >> > > |
| > >> > > | "Murray" wrote:
| > >> > > |
| > >> > > | > Uhhh - post a link to YOUR pge - the one that is giving you
| > >> problems....
| > >> > > | >
| > >> > > | > --
| > >> > > | > Murray
| > >> > > | > ============
| > >> > > | >
message
| > >> > > | > | > >> > > | > >
| > >> > > | > > http://www.w3schools.com/site/site_validate.asp
| > >> > > | > > Thanks
| > >> > > | > >
| > >> > > | > > --
| > >> > > | > > Vanilla
| > >> > > | > > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > >> > > | > > http://www.searchenginelocator.com
| > >> > > | > > "From one small seed of kindness ... friendship grows."
| > >> > > | > >
| > >> > > | > >
| > >> > > | > > "Murray" wrote:
| > >> > > | > >
| > >> > > | > >> Just post a link to the page, please.
| > >> > > | > >>
| > >> > > | > >> --
| > >> > > | > >> Murray
| > >> > > | > >> ============
| > >> > > | > >>
| > >> message
| > >> > > | > >> | > >> > > | > >> >I thought that I followed your instructions, but probably
| > >> I'm doing
| > >> > > | > >> >something
| > >> > > | > >> > wrong, because I am back to 182 errors! Here is the
| > >> result. I
| > >> > > | > >> > appriciate
| > >> > > | > >> > your help.
| > >> > > | > >> > Result--just part of it--: Failed validation, 182 errors
| > >> > > | > >> > Address:
| > >> > > | > >> > Encoding: iso-8859-1 (detect automatically) utf-8
| > >> (Unicode, worldwide)
| > >> > > | > >> > utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe)
| > >> iso-8859-2
| > >> > > | > >> > (Central
| > >> > > | > >> > Europe) iso-8859-3 (Southern Europe) iso-8859-4 (Baltic
| > >> Rim) iso-8859-5
| > >> > > | > >> > (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek)
| > >> iso-8859-8-i
| > >> > > | > >> > (Hebrew)
| > >> > > | > >> > iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-13
| > >> (Latin 7)
| > >> > > | > >> > iso-8859-14
| > >> > > | > >> > (Celtic) iso-8859-15 (Latin 9) us-ascii (basic English)
| > >> euc-jp
| > >> > > | > >> > (Japanese,
| > >> > > | > >> > Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp
| > >> (Japanese, email)
| > >> > > | > >> > euc-kr
| > >> > > | > >> > (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese,
| > >> simplified)
| > >> > > | > >> > big5
| > >> > > | > >> > (Chinese, traditional) tis-620 (Thai) koi8-r (Russian)
| > >> koi8-u
| > >> > > | > >> > (Ukrainian)
| > >> > > | > >> > macintosh (MacRoman) windows-1250 (Central Europe)
| > >> windows-1251
| > >> > > | > >> > (Cyrillic)
| > >> > > | > >> > windows-1252 (Western Europe) windows-1253 (Greek)
| > >> windows-1254
| > >> > > | > >> > (Turkish)
| > >> > > | > >> > windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257
| > >> (Baltic Rim)
| > >> > > | > >> > Doctype: (no Doctype found) (detect automatically)
XHTML
| > >> 1.1 XHTML
| > >> > > | > >> > Basic
| > >> > > | > >> > 1.0 XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0
| > >> Frameset ISO/IEC
| > >> > > | > >> > 15445:2000 ("ISO HTML") HTML 4.01 Strict HTML 4.01
| > >> Transitional HTML
| > >> > > | > >> > 4.01
| > >> > > | > >> > Frameset HTML 3.2 HTML 2.0 MathML 2.0 XHTML 1.1 plus
| > >> MathML 2.0
| > >> > > | > >> > Revalidate With Options: Show Source Show Outline
| > >> > > | > >> > Show Parse Tree ...no attributes
| > >> > > | > >> > Validate error pages Verbose Output
| > >> > > | > >> >
| > >> > > | > >> > Help on the options is available.
| > >> > > | > >> >
| > >> > > | > >> > No DOCTYPE found! Attempting validation with HTML 4.01
| > >> Transitional.
| > >> > > | > >> > The
| > >> > > | > >> > DOCTYPE Declaration was not recognized or is missing.
| > >> This probably
| > >> > > | > >> > means
| > >> > > | > >> > that the Formal Public Identifier contains a spelling
| > >> error, or that
| > >> > > | > >> > the
| > >> > > | > >> > Declaration is not using correct syntax. Validation has
| > >> been performed
| > >> > > | > >> > using
| > >> > > | > >> > a default "fallback" Document Type Definition that
| > >> closely resembles
| > >> > > | > >> > "HTML
| > >> > > | > >> > 4.01 Transitional", but the document will not be Valid
| > >> until you have
| > >> > > | > >> > corrected this problem with the DOCTYPE Declaration.
| > >> > > | > >> >
| > >> > > | > >> > Learn how to add a doctype to your document from our
FAQ.
| > >> > > | > >> >
| > >> > > | > >> > This page is not Valid (no Doctype found)!
| > >> > > | > >> > Below are the results of attempting to parse this
| > >> document with an SGML
| > >> > > | > >> > parser.
| > >> > > | > >> >
| > >> > > | > >> > Error Line 1 column 0: no document type declaration;
| > >> implying
| > >> > > | > >> > "<!DOCTYPE
| > >> > > | > >> > HTML SYSTEM>".
| > >> > > | > >> > <html><head><meta http-equiv="Content-Type"
| > >> content="text/html;
| > >> > > | > >> > charset=iso-8859
| > >> > > | > >> > The checked page did not contain a document type
| > >> ("DOCTYPE")
| > >> > > | > >> > declaration.
| > >> > > | > >> > The Validator has tried to validate with a fallback DTD,
| > >> but this is
| > >> > > | > >> > quite
| > >> > > | > >> > likely to be incorrect and will generate a large number
| > >> of incorrect
| > >> > > | > >> > error
| > >> > > | > >> > messages. It is highly recommended that you insert the
| > >> proper DOCTYPE
| > >> > > | > >> > declaration in your document -- instructions for doing
| > >> this are given
| > >> > > | > >> > above
| > >> > > | > >> > -- and it is necessary to have this declaration before
| > >> the page can be
| > >> > > | > >> > declared to be valid.
| > >> > > | > >> >
| > >> > > | > >> > ?
| > >> > > | > >> >
| > >> > > | > >> > Error Line 1 column 216: there is no attribute
| > >> "TOPMARGIN".
| > >> > > | > >> > ...ad><body bgcolor="#E6E6FF" topmargin="00"><table
| > >> cellpadding="0"
| > >> > > | > >> > cellspacing=
| > >> > > | > >> > 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

Vanilla · Dec 17, 2005

Thanks Bob, I did not realize that I've lost my "head".
--
Vanilla
Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
http://www.searchenginelocator.com
"From one small seed of kindness ... friendship grows."

Bob said:
A quick glance netted this....

Missing is <head> (After the <HTML> tag and </head> (before the <Body> tag

This is why the <body> tag is in the wrong place.

Also---
<body bgcolor="#E6E6FF">
<bgcolor="#E6E6FF">
you only need to declare the color once...

This will give you a start....

HTH

Bob
| my website: http://www.searchenginelocator.com
| --
| Vanilla
| Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| my website: http://www.searchenginelocator.com
| "From one small seed of kindness ... friendship grows."
|
|
| "Murray" wrote:
|
| > > I thought that FrontPage is using HTML.
| >
| > It is. The error probably means that the page doesn't have a valid and
| > complete doctype.
| >
| > > 2.)Every error is identified by their 'where-abouts': x line y column.
My
| > > question is that what the 'column' is referring to?
| >
| > Ignore it, usually. Sometimes it would be the number of characters to
the
| > right of the left margin.
| >
| > > 3.) "Line 8 column 23: document type does not allow element "BODY"
here.
| > > <body bgcolor="#E6E6FF">"
| >
| > I would have to see the page to tell you why this is.
| >
| > --
| > Murray
| > ============
| >
| > | > >I did what Ronx suggested (thanks) but it did not change-or I did not
| > >realize
| > > that it did as the numbers of errors were the same--my error report.
| > > Right now I'm working on my webpage using the validation test. 184
errors
| > > are down to 124.
| > > I try to make sense of the explanations that follow every error.
There
| > > are
| > > things (a lot) that I could not figure out myself & need some help
with
| > > it.
| > > 1.) "This page is not Valid HTML 4.01 Transitional! Below are the
results
| > > of attempting to parse this document with an SGML parser."
| > >
| > > I thought that FrontPage is using HTML.
| > >
| > > 2.)Every error is identified by their 'where-abouts': x line y column.
My
| > > question is that what the 'column' is referring to?
| > >
| > > 3.) "Line 8 column 23: document type does not allow element "BODY"
here.
| > > <body bgcolor="#E6E6FF">"
| > >
| > > It was created by Frontpage 2003 while I used WYSIWYG option.
| > > I deleted it but it appeared again when I defined the page colour.
| > >
| > >
| > > Thanks guys & galls for all your helps.
| > >
| > > --
| > > Vanilla
| > > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > > http://www.searchenginelocator.com
| > > "From one small seed of kindness ... friendship grows."
| > >
| > >
| > > "Ronx" wrote:
| > >
| > >> First, open the web and then the page in FrontPage.
| > >> Got to Code view
| > >> Change
| > >> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
| > >> "http://www.searchenginelcoator.com"><meta
| > >> http-equiv="Content-Type" content="text/html;
| > >> charset=iso-8859-1"><html><head><meta http-equiv="Content-Type"
| > >> content="text/html; charset=iso-8859-1">
| > >> to
| > >> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
| > >> "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
| > >> <html><head><meta http-equiv="Content-Type" content="text/html;
| > >> charset=iso-8859-1">
| > >>
| > >> Then right click anywhere in the code and choose Reformat HTML.
| > >> When you republish the page, before hitting the publish button, click
| > >> on Optimise Published HTML... and clear ALL the check boxes.
| > >>
| > >> Then publish and try the validation check.
| > >> Your page currently has all white space removed, which makes it
| > >> impossible to see what is going on.
| > >> --
| > >> Ron Symonds - Microsoft MVP (FrontPage)
| > >> Reply only to group - emails will be deleted unread.
| > >> FrontPage Support: http://www.frontpagemvps.com/
| > >>
| > >>
| > >> | > >> > I appriciate your concern. I've had the validation test and failed
| > >> again.
| > >> > Every time I fail, I get more errors. Now I am up to 184.
| > >> > I'm sure that somebody has the answer out there. I appriciate any
| > >> thoguths
| > >> > on this subject.
| > >> > Thank you
| > >> > Vanilla, http://www.searchenginelocator.com
| > >> > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > >> > "From one small seed of kindness ... friendship grows."
| > >> >
| > >> >
| > >> > "Stefan B Rusynko" wrote:
| > >> >
| > >> > > Start in code view and add the doc type per Murray's instructions
| > >> > > Check your pages using Tools Browser Compatibility
| > >> > > Then Turn off the Optimize html options and republish your site
| > >> > >
| > >> > > PS
| > >> > > you will never get a complete validation as long as you are using
| > >> FP design time webbots
| > >> > > - but the errors you get from them will not prevent the pages
| > >> from being correct
| > >> > >
| > >> > > --
| > >> > >
| > >> > > _____________________________________________
| > >> > > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > >> > > "Warning - Using the F1 Key will not break anything!" (-;
| > >> > > To find the best Newsgroup for FrontPage support see:
| > >> > >
| > >>
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
| > >> > > _____________________________________________
| > >> > >
| > >> > >
| > >> | > >> > > | http://www.searchenginelocator.com
| > >> > > | --
| > >> > > | Vanilla
| > >> > > | Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > >> > > | http://www.searchenginelocator.com
| > >> > > | "From one small seed of kindness ... friendship grows."
| > >> > > |
| > >> > > |
| > >> > > | "Murray" wrote:
| > >> > > |
| > >> > > | > Uhhh - post a link to YOUR pge - the one that is giving you
| > >> problems....
| > >> > > | >
| > >> > > | > --
| > >> > > | > Murray
| > >> > > | > ============
| > >> > > | >
message
| > >> > > | > | > >> > > | > >
| > >> > > | > > http://www.w3schools.com/site/site_validate.asp
| > >> > > | > > Thanks
| > >> > > | > >
| > >> > > | > > --
| > >> > > | > > Vanilla
| > >> > > | > > Using: MW 2003, Excell 2003, Publisher 2003, FP 2003,
| > >> > > | > > http://www.searchenginelocator.com
| > >> > > | > > "From one small seed of kindness ... friendship grows."
| > >> > > | > >
| > >> > > | > >
| > >> > > | > > "Murray" wrote:
| > >> > > | > >
| > >> > > | > >> Just post a link to the page, please.
| > >> > > | > >>
| > >> > > | > >> --
| > >> > > | > >> Murray
| > >> > > | > >> ============
| > >> > > | > >>
| > >> message
| > >> > > | > >> | > >> > > | > >> >I thought that I followed your instructions, but probably
| > >> I'm doing
| > >> > > | > >> >something
| > >> > > | > >> > wrong, because I am back to 182 errors! Here is the
| > >> result. I
| > >> > > | > >> > appriciate
| > >> > > | > >> > your help.
| > >> > > | > >> > Result--just part of it--: Failed validation, 182 errors
| > >> > > | > >> > Address:
| > >> > > | > >> > Encoding: iso-8859-1 (detect automatically) utf-8
| > >> (Unicode, worldwide)
| > >> > > | > >> > utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe)
| > >> iso-8859-2
| > >> > > | > >> > (Central
| > >> > > | > >> > Europe) iso-8859-3 (Southern Europe) iso-8859-4 (Baltic
| > >> Rim) iso-8859-5
| > >> > > | > >> > (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek)
| > >> iso-8859-8-i
| > >> > > | > >> > (Hebrew)
| > >> > > | > >> > iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-13
| > >> (Latin 7)
| > >> > > | > >> > iso-8859-14
| > >> > > | > >> > (Celtic) iso-8859-15 (Latin 9) us-ascii (basic English)
| > >> euc-jp
| > >> > > | > >> > (Japanese,
| > >> > > | > >> > Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp
| > >> (Japanese, email)
| > >> > > | > >> > euc-kr
| > >> > > | > >> > (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese,
| > >> simplified)
| > >> > > | > >> > big5
| > >> > > | > >> > (Chinese, traditional) tis-620 (Thai) koi8-r (Russian)
| > >> koi8-u
| > >> > > | > >> > (Ukrainian)
| > >> > > | > >> > macintosh (MacRoman) windows-1250 (Central Europe)
| > >> windows-1251
| > >> > > | > >> > (Cyrillic)
| > >> > > | > >> > windows-1252 (Western Europe) windows-1253 (Greek)
| > >> windows-1254
| > >> > > | > >> > (Turkish)
| > >> > > | > >> > windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257
| > >> (Baltic Rim)
| > >> > > | > >> > Doctype: (no Doctype found) (detect automatically)
XHTML
| > >> 1.1 XHTML
| > >> > > | > >> > Basic
| > >> > > | > >> > 1.0 XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0
| > >> Frameset ISO/IEC
| > >> > > | > >> > 15445:2000 ("ISO HTML") HTML 4.01 Strict HTML 4.01
| > >> Transitional HTML
| > >> > > | > >> > 4.01
| > >> > > | > >> > Frameset HTML 3.2 HTML 2.0 MathML 2.0 XHTML 1.1 plus
| > >> MathML 2.0
| > >> > > | > >> > Revalidate With Options: Show Source Show Outline
| > >> > > | > >> > Show Parse Tree ...no attributes
| > >> > > | > >> > Validate error pages Verbose Output
| > >> > > | > >> >
| > >> > > | > >> > Help on the options is available.
| > >> > > | > >> >
| > >> > > | > >> > No DOCTYPE found! Attempting validation with HTML 4.01
| > >> Transitional.
| > >> > > | > >> > The
| > >> > > | > >> > DOCTYPE Declaration was not recognized or is missing.
| > >> This probably
| > >> > > | > >> > means
| > >> > > | > >> > that the Formal Public Identifier contains a spelling
| > >> error, or that
| > >> > > | > >> > the
| > >> > > | > >> > Declaration is not using correct syntax. Validation has
| > >> been performed
| > >> > > | > >> > using
| > >> > > | > >> > a default "fallback" Document Type Definition that
| > >> closely resembles
| > >> > > | > >> > "HTML
| > >> > > | > >> > 4.01 Transitional", but the document will not be Valid
| > >> until you have
| > >> > > | > >> > corrected this problem with the DOCTYPE Declaration.
| > >> > > | > >> >
| > >> > > | > >> > Learn how to add a doctype to your document from our
FAQ.
| > >> > > | > >> >
| > >> > > | > >> > This page is not Valid (no Doctype found)!
| > >> > > | > >> > Below are the results of attempting to parse this
| > >> document with an SGML
| > >> > > | > >> > parser.
| > >> > > | > >> >
| > >> > > | > >> > Error Line 1 column 0: no document type declaration;
| > >> implying
| > >> > > | > >> > "<!DOCTYPE
| > >> > > | > >> > HTML SYSTEM>".
| > >> > > | > >> > <html><head><meta http-equiv="Content-Type"
| > >> content="text/html;
| > >> > > | > >> > charset=iso-8859
| > >> > > | > >> > The checked page did not contain a document type
| > >> ("DOCTYPE")
| > >> > > | > >> > declaration.
| > >> > > | > >> > The Validator has tried to validate with a fallback DTD,

Force Character Encoding	9	Jan 7, 2010
Why so many blank lines?	2	Mar 10, 2009
php	4	Jul 20, 2009
invalid character	3	May 13, 2009
outlook 2003 mailto: display issue for UTF-8 chars (thru IE6)	1	Jan 26, 2011
Import site created in NetFusion with Flash	1	Jan 3, 2007
Is there another way to do this so it will validate.	32	Feb 27, 2007
XHTML Validation by w3c	6	Jan 11, 2006

"No character encoding found, No doctype found"

Vanilla

Murray

Vanilla

Murray

Vanilla

Murray

Vanilla

Stefan B Rusynko

Vanilla

Ronx

Vanilla

Murray

Vanilla

Bob

Vanilla

Ask a Question

Similar Threads