hello,
i validate www.bluekrawatte.at and i appears without amistakes but
when i add the address which links the page direct to the validator
results, i get 9 mistakes, and all of then come from the url for the
validator this is what i get (look below)
but when ckecking the url direct online i get not errors, i took a
look and the error comes for the validator url.
http://validator.w3.org/check?uri=www.bluekrawatte.at&charset=%28detect+automatically%29&doctype=Inline&group=0
thanks
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Jump To:
Validation Output
Errors found while checking this document as XHTML 1.0 Transitional!
Result: 9 Errors, 9 warning(s)
Address:
Encoding: utf-8
Doctype: XHTML 1.0 Transitional
Root Element: html
Root Namespace: http://www.w3.org/1999/xhtml
The W3C validators are hosted on server technology donated by HP, and
supported by community donations.
Donate and help us build better tools for a better web.
Options
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.
↑ Top
Validation Output: 9 Errors
Line 125, Column 258: cannot generate system identifier for general
entity "charset"
…3.org/check?uri=www.bluekrawatte.at&charset=%28detect+automatically
%29&doctyp
✉
An 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 "&amp;" (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 &aelig;
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 125, Column 258: general entity "charset" not defined and no
default entity
…3.org/check?uri=www.bluekrawatte.at&charset=%28detect+automatically
%29&doctyp
✉
This 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 125, Column 265: reference not terminated by REFC delimiter
…heck?uri=www.bluekrawatte.at&charset=%28detect+automatically
%29&doctype=Inlin
✉
If you meant to include an entity that starts with "&", then you
should terminate it with ";". Another reason for this error message is
that you inadvertently created an entity by failing to escape an "&"
character just before this text.
Line 125, Column 265: reference to external entity in attribute value
…heck?uri=www.bluekrawatte.at&charset=%28detect+automatically
%29&doctype=Inlin
✉
This is generally the sign of an ampersand that was not properly
escaped for inclusion in an attribute, in a href for example. You will
need to escape all instances of '&' into '&amp;'.
Line 125, Column 265: reference to entity "charset" for which no
system identifier could be generated
…heck?uri=www.bluekrawatte.at&charset=%28detect+automatically
%29&doctype=Inlin
✉
This 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 125, Column 256: entity was defined here
….w3.org/check?uri=www.bluekrawatte.at&charset=%28detect+automatically
%29&doct
Line 125, Column 293: cannot generate system identifier for general
entity "doctype"
…&charset=%28detect+automatically%29&doctype=Inline&group=0"> <img
src="images
✉
An 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 "&amp;" (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 &aelig;
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 125, Column 293: general entity "doctype" not defined and no
default entity
…&charset=%28detect+automatically%29&doctype=Inline&group=0"> <img
src="images
✉
This 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 125, Column 300: reference not terminated by REFC delimiter
…t=%28detect+automatically%29&doctype=Inline&group=0"> <img
src="images/valid-
✉
If you meant to include an entity that starts with "&", then you
should terminate it with ";". Another reason for this error message is
that you inadvertently created an entity by failing to escape an "&"
character just before this text.
Line 125, Column 300: reference to external entity in attribute value
…t=%28detect+automatically%29&doctype=Inline&group=0"> <img
src="images/valid-
✉
This is generally the sign of an ampersand that was not properly
escaped for inclusion in an attribute, in a href for example. You will
need to escape all instances of '&' into '&amp;'.
Line 125, Column 300: reference to entity "doctype" for which no
system identifier could be generated
…t=%28detect+automatically%29&doctype=Inline&group=0"> <img
src="images/valid-
✉
This 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 125, Column 291: entity was defined here
…at&charset=%28detect+automatically%29&doctype=Inline&group=0"> <img
src="imag
Line 125, Column 308: cannot generate system identifier for general
entity "group"
…ect+automatically%29&doctype=Inline&group=0"> <img src="images/valid-
xhtml10-
✉
An 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 "&amp;" (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 &aelig;
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 125, Column 308: general entity "group" not defined and no
default entity
…ect+automatically%29&doctype=Inline&group=0"> <img src="images/valid-
xhtml10-
✉
This 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 125, Column 313: reference not terminated by REFC delimiter
…utomatically%29&doctype=Inline&group=0"> <img src="images/valid-
xhtml10-blue.
✉
If you meant to include an entity that starts with "&", then you
should terminate it with ";". Another reason for this error message is
that you inadvertently created an entity by failing to escape an "&"
character just before this text.
Line 125, Column 313: reference to external entity in attribute value
…utomatically%29&doctype=Inline&group=0"> <img src="images/valid-
xhtml10-blue.
✉
This is generally the sign of an ampersand that was not properly
escaped for inclusion in an attribute, in a href for example. You will
need to escape all instances of '&' into '&amp;'.
Line 125, Column 313: reference to entity "group" for which no
system identifier could be generated
…utomatically%29&doctype=Inline&group=0"> <img src="images/valid-
xhtml10-blue.
✉
This 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 125, Column 306: entity was defined here
…etect+automatically%29&doctype=Inline&group=0"> <img src="images/
valid-xhtml1
NOTE: Whenever possible, give the address of the document you were
checking.