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.
Missing "
charset
" attribute for
"text/xml
" document.
The HTTP Content-Type
header
(text/xml
) sent by your web
server
(Apache
) did not contain
a "charset
" parameter, but the Content-Type was one of
the XML text/*
sub-types.
The relevant specification
(RFC 3023)
specifies a strong default of "us-ascii
" for
such documents so we will use this value regardless of any encoding you
may have indicated elsewhere.
If you would like to use a different encoding, you should arrange to have your server send this new encoding information.
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.
I could not parse this document, because it makes reference to a system-specific file instead of using a well-known public identifier to specify the type of markup being used.
You should place a DOCTYPE declaration as the very first thing in your HTML document. For example, for a typical XHTML 1.0 document:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head> <title>Title</title> </head> <body> <!-- ... body of document ... --> </body> </html>
For XML documents, you may also wish to include an "XML Declaration" even before the DOCTYPE Declaration, but this is not well supported in older browsers. More information about this can be found in the XHTML 1.0 Recommendation.