T
thedarkman
Congratulations
I created that file exactly as you said, and although it validates, it
says you made 3 errors. I'm assuming you know what you are doing but
the validator does not. It appears just as there is no pleasing some
people there is no pleasing some software programs, therefore I will
not try to please it anymore.
One query about Doc type. Does this apply to all current .htm
and .html files? Or when html is "upgraded" are we supposed to alter
everything?
I've been on-line more than 10 years now and have problems with only a
handful of files and then not with all browsers, so ignorant though I
may be, that is not a bad track record.
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.
No Character Encoding Found! Falling back to UTF-8.
None of the standards sources gave any information on the character
encoding labeling for this document. Without encoding information it
is impossible to reliably validate the document. As a fallback
solution, the "UTF-8" encoding was used to read the content and
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.
Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types
such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions).
For this document, the information available was not sufficient to
determine the parsing mode unambiguously, because:
the MIME Media Type (text/html) can be used for XML or SGML document
types
the Document Type (-//W3C//DTD HTML 3.2//EN) is not in the validator's
catalog
No XML declaration (e.g <?xml version="1.0"?>) could be found at the
beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
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.
The document located at <http://www.infotextmanuscripts.org/
1_son.html> was tentatively checked as -//W3C//DTD HTML 3.2//EN. This
means that with the use of some fallback or override mechanism, we
successfully performed a formal validation of it. In other words, the
document would validate as -//W3C//DTD HTML 3.2//EN if you changed the
markup to match the changes we have performed automatically, but it
will not be valid until you make these changes. The parser
implementations we used for this check are based on OpenSP (SGML/XML).
Linking to this result
If you would like to create a link to this page (i.e., this validation
result) to make it easier to revalidate this page in the future or to
allow others to validate your page, the URI is <http://
validator.w3.org/check?uri=http%3A%2F%2Fwww.infotextmanuscripts.org
%2F1_son.html> (or you can just add the current page to your bookmarks
or hotlist).
Validating CSS Style Sheets
I created that file exactly as you said, and although it validates, it
says you made 3 errors. I'm assuming you know what you are doing but
the validator does not. It appears just as there is no pleasing some
people there is no pleasing some software programs, therefore I will
not try to please it anymore.
One query about Doc type. Does this apply to all current .htm
and .html files? Or when html is "upgraded" are we supposed to alter
everything?
I've been on-line more than 10 years now and have problems with only a
handful of files and then not with all browsers, so ignorant though I
may be, that is not a bad track record.
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.
No Character Encoding Found! Falling back to UTF-8.
None of the standards sources gave any information on the character
encoding labeling for this document. Without encoding information it
is impossible to reliably validate the document. As a fallback
solution, the "UTF-8" encoding was used to read the content and
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.
Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types
such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions).
For this document, the information available was not sufficient to
determine the parsing mode unambiguously, because:
the MIME Media Type (text/html) can be used for XML or SGML document
types
the Document Type (-//W3C//DTD HTML 3.2//EN) is not in the validator's
catalog
No XML declaration (e.g <?xml version="1.0"?>) could be found at the
beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
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.
The document located at <http://www.infotextmanuscripts.org/
1_son.html> was tentatively checked as -//W3C//DTD HTML 3.2//EN. This
means that with the use of some fallback or override mechanism, we
successfully performed a formal validation of it. In other words, the
document would validate as -//W3C//DTD HTML 3.2//EN if you changed the
markup to match the changes we have performed automatically, but it
will not be valid until you make these changes. The parser
implementations we used for this check are based on OpenSP (SGML/XML).
Linking to this result
If you would like to create a link to this page (i.e., this validation
result) to make it easier to revalidate this page in the future or to
allow others to validate your page, the URI is <http://
validator.w3.org/check?uri=http%3A%2F%2Fwww.infotextmanuscripts.org
%2F1_son.html> (or you can just add the current page to your bookmarks
or hotlist).
Validating CSS Style Sheets
