[Invalid] Markup Validation of palautus_main.html - W3C Markup Validator
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Errors found while checking this document as HTML 4.01 Transitional!
| Result: | 6 Errors, 7 warning(s) | |
|---|---|---|
| File: |
Use the file selection box above if you wish to re-validate the uploaded file palautus_main.html |
|
| Encoding: | windows-1252 | (detect automatically) utf-8 (Unicode, worldwide) utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European) iso-8859-5 (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew, visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-11 (Latin/Thai) iso-8859-13 (Latin 7, Baltic Rim) iso-8859-14 (Latin 8, Celtic) iso-8859-15 (Latin 9) iso-8859-16 (Latin 10) us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional) Big5-HKSCS (Chinese, Hong Kong) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian) iso-ir-111 (Cyrillic KOI-8) macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim) |
| Doctype: | HTML 4.01 Transitional | (detect automatically) HTML5 (experimental) XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset HTML 3.2 HTML 2.0 ISO/IEC 15445:2000 ("ISO HTML") XHTML 1.1 XHTML + RDFa XHTML Basic 1.0 XHTML Basic 1.1 XHTML Mobile Profile 1.2 XHTML-Print 1.0 XHTML 1.1 plus MathML 2.0 XHTML 1.1 plus MathML 2.0 plus SVG 1.1 MathML 2.0 SVG 1.0 SVG 1.1 SVG 1.1 Tiny SVG 1.1 Basic SMIL 1.0 SMIL 2.0 |
| Root Element: | html | |
| Show Source | Show Outline | List Messages Sequentially Group Error Messages by Type |
| Validate error pages | Verbose Output | Clean up Markup with HTML Tidy |
Help on the options is available.
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. 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
windows-1252.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 "
windows-1252" encoding was used to read the content and attempt to perform the validation, but this is likely to fail for all non-trivial documents.Before defaulting to
windows-1252the validator also tried to read the content with the following encoding(s), without success:UTF-8.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 - No known Document Type could be detected
- 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.
-
the MIME Media Type (
- No
DOCTYPEfound! Checking with default HTML 4.01 Transitional Document Type.No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.
The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.
Learn how to add a doctype to your document from our FAQ.
No Character encoding declared at document levelNo character encoding information was found within the document, either in an HTML
metaelement 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.
Validation Output: 6 Errors
-
Line 1, Column 1:
no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<html>The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
-
Line 4, Column 7:
end tag for "HEAD" which is not finished
</head>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
-
Line 9, Column 91:
cannot generate system identifier for general entity "ws"
…emnoborder" href="doc_show?id=18745&ws=18683&name=/Palautuslaatikko"> > PaAn 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 9, Column 91:
general entity "ws" not defined and no default entity
…emnoborder" href="doc_show?id=18745&ws=18683&name=/Palautuslaatikko"> > PaThis 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 9, Column 93:
reference to entity "ws" for which no system identifier could be generated
…noborder" href="doc_show?id=18745&ws=18683&name=/Palautuslaatikko"> > PalaThis 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 9, Column 89:
entity was defined here
…itemnoborder" href="doc_show?id=18745&ws=18683&name=/Palautuslaatikko"> > -
Line 9, Column 100:
cannot generate system identifier for general entity "name"
…r" href="doc_show?id=18745&ws=18683&name=/Palautuslaatikko"> > PalautuslaaAn 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 9, Column 100:
general entity "name" not defined and no default entity
…r" href="doc_show?id=18745&ws=18683&name=/Palautuslaatikko"> > PalautuslaaThis 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 9, Column 104:
reference to entity "name" for which no system identifier could be generated
…ref="doc_show?id=18745&ws=18683&name=/Palautuslaatikko"> > PalautuslaatikkThis 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 9, Column 98:
entity was defined here
…der" href="doc_show?id=18745&ws=18683&name=/Palautuslaatikko"> > Palautusl
