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.
No Character Encoding Found!
Using
(detect.
None of the standards sources gave any information on the character encoding labeling for this document. The character
encoding (detect,
which you have chosen via the Encoding override option, will be used for tentative validation.
Read the FAQ entry on character encoding for more details and pointers on how to fix this problem with your document.
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.
A fatal error occurred when attempting to transcode the character encoding of the document. Either we do not support this character encoding ("(detect") yet, or you have specified a non-existent character encoding (often a misspelling).
The error was: Encoding not supported.
If you believe the character encoding to be valid you can submit a request for that character encoding (see the feedback page for details) and we will look into supporting it in the future.
IANA maintains the list of official names for character sets and the WDG has some information to help you correctly specify the character encoding.