XHTML and HTML

**Vasili** · 09-21-2010, 02:46 AM

Re: XHTML and HTML

Broken Links are broken links: they can be fixed manaully without respect to difference in coding, especially eclectic coding when using a web builder, in particular Blue Voda (it is likened to "swallowing a camel but straining on a gnat.").

List any code errors specifically for a proper reply with respect to your site.

**Paulk2** · 09-22-2010, 11:14 PM

Re: XHTML and HTML

Hi Vasili,
Here's a string of output from the Validator regarding my site www.americaneaglesigning.com/index.html:

Line 27, Column 93: NET-enabling start-tag requires SHORTTAG YES �gle-site-verification" content="aqkxaKc32JktABzWtkuk7gQh3swZA9Su5gWtRDphE MY" /> ✉
The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 126, Column 23: document type does not allow element "STYLE" here <style type="text/css"> ✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 129, Column 7: end tag for element "HEAD" which is not open </head> ✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 130, Column 63: document type does not allow element "BODY" here <body background="108b48.jpg" bgcolor="#FFFFFF" text="#000000"> ✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 159, Column 4: end tag for "B" omitted, but its declaration does not permit this </i></b></font></div> ✉
- 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.
Line 158, Column 1: start tag was here <b>"We are not attorneys licensed to practice law in the State of Florida.�
Line 159, Column 8: end tag for element "B" which is not open </i></b></font></div> ✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 213, Column 56: cannot generate system identifier for general entity "sURL" �ww.legalzoom.com/jump.asp?iRefer=4057&sURL=/index.html"><img src="images/Legal� ✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 213, Column 56: general entity "sURL" not defined and no default entity �ww.legalzoom.com/jump.asp?iRefer=4057&sURL=/index.html"><img src="images/Legal� ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 213, Column 60: reference to entity "sURL" for which no system identifier could be generated �egalzoom.com/jump.asp?iRefer=4057&sURL=/index.html"><img src="images/LegalZoom� ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 213, Column 55: entity was defined here �www.legalzoom.com/jump.asp?iRefer=4057&sURL=/index.html"><img src="images/Lega�
Line 216, Column 71: end tag for "I" omitted, but its declaration does not permit this <i><a href="http://www.bluevoda.com">VodaHost website builder</a></div> ✉
- 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.
Line 216, Column 1: start tag was here <i><a href="http://www.bluevoda.com">VodaHost website builder</a></div>
Line 216, Column 71: end tag for "CENTER" omitted, but its declaration does not permit this <i><a href="http://www.bluevoda.com">VodaHost website builder</a></div> ✉
- 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.
Line 215, Column 1: start tag was here <center>

**Vasili** · 09-23-2010, 02:32 AM

Re: XHTML and HTML

Just saw this .... give me until tomorrow to reply: I have a must-do thing in front of me now, and you deserve a more detailed reply than I can provide at the moment.

(Too bad you do not "service" P.H./34685 .... I live in the Boot Ranch area, and we could do this face to face!)

**Paulk2** · 09-23-2010, 03:26 AM

Re: XHTML and HTML

Thanks Vasili!

I think I have some of them figured out but haven't changed anything yet. I'll be looking forward to your input. Thanks again!

XHTML and HTML

XHTML and HTML

Comment

Comment

Comment

Comment