Home » RADICORE development » Bug Reports » sample v3.0.0 XHTML markup errors
| Re: sample v3.0.0 XHTML markup errors [message #3317 is a reply to message #3314] |
Sat, 12 January 2013 13:53   |
jjtoranzo2004
Messages: 261
Registered: September 2012
|
Senior Member |
|
|
Tony,
Thanks for fixing everything.
I checked
http://www.tonymarston.net/sample/help.php?session_name=samp le&taskid=person_list.php
with the W3C Markup Validation Service (http://validator.w3.org/).
Pe
It found the following errors:
-------------------------
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Warning Mismatch between Public and System identifiers in the DOCTYPE declaration
This document uses an inconsistent DOCTYPE declaration. The Public Identifier -//W3C//DTD HTML 4.0 Transitional//EN declares the HTML 4.0 Transitional document type, but the associated System Identifier http://www.w3.org/TR/html4/loose.dtd does not match this document type.
The recommended System Identifier for HTML 4.0 Transitional is http://www.w3.org/TR/1998/REC-html40-19980424/loose.dtd.
The safest way to use a correct DOCTYPE declaration is to copy and paste one from the recommended list and avoid editing that part of your markup by hand.
Info No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.
↑ Top
Validation Output: 4 Errors
Error Line 2, Column 16: there is no attribute "XML:LANG"
<html xml:lang='' lang=''>
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Error Line 2, Column 25: syntax of attribute value does not conform to declared value
<html xml:lang='' lang=''>
✉
The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the "selected" attribute must be either minimized as "selected" or spelled out in full as "selected="selected""; the variant "selected=""" is not allowed.
Warning Line 5, Column 58: NET-enabling start-tag requires SHORTTAG YES
<link rel='stylesheet' type='text/css' href='help.css' />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
Error Line 6, 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.
Error Line 7, Column 6: document type does not allow element "BODY" here
<body>
✉
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).
Warning Line 11, Column 48: NET-enabling start-tag requires SHORTTAG YES
... list records on the PERSON table.<br /><br />For a description of screens of ...
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
Warning Line 11, Column 54: NET-enabling start-tag requires SHORTTAG YES
...records on the PERSON table.<br /><br />For a description of screens of type L...
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
-------------------------
Perhaps you could convert help pages to XTHML.
Thanks.
|
|
|
|
Current Time: Sat Nov 23 12:33:05 EST 2024
Total time taken to generate the page: 0.01288 seconds
|
Radicore Forum
Search
Help
Members
Register
Login
Home
