problemer med at rette fejl fra Markup Validation Service
Jeg undrer mig over at få flg to kategorier af fejl:Den en, fx:
Line 38, Column 42: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?
Line 43, Column 77: Attribute "BACKGROUND" is not a valid attribute. Did you mean "background"
Line 96, Column 100: Attribute "VALIGN" is not a valid attribute. Did you mean "valign"?
i de tre ovenfor pastede tilfælde (og flere til) skriver jeg nemlig i forvejen med småt i koderne. Så hvad gør man?
------------------
Den anden kategori af fejl, drejer sig om link til krak.dk.
Jeg får flg. fejlmelding, der undrer mig, for dels fungerer linket i praksis (Se http://www.yes-yes.dk/Mulvad-2/), dels, ved jeg ikke hvad man ellers skulle gøre.
Alt det herfra pastede er validatorens reaktion på et enkelt krak.dk link:
Line 134, Column 116: cannot generate system identifier for general entity "search_word"
…f="http://www.krak.dk/query?what=wp&search_word=ruth+mulvad&geo_area=')" targ
✉
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 "&" (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 134, Column 116: general entity "search_word" not defined and no default entity
…f="http://www.krak.dk/query?what=wp&search_word=ruth+mulvad&geo_area=')" targ
✉
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 134, Column 127: reference to entity "search_word" for which no system identifier could be generated
…ww.krak.dk/query?what=wp&search_word=ruth+mulvad&geo_area=')" target="_blank"
✉
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 134, Column 114: entity was defined here
…ref="http://www.krak.dk/query?what=wp&search_word=ruth+mulvad&geo_area=')" ta
Line 134, Column 140: cannot generate system identifier for general entity "geo_area"
…ery?what=wp&search_word=ruth+mulvad&geo_area=')" target="_blank">Engkrogen 30
✉
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 "&" (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 134, Column 140: general entity "geo_area" not defined and no default entity
…ery?what=wp&search_word=ruth+mulvad&geo_area=')" target="_blank">Engkrogen 30
✉
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 134, Column 148: reference to entity "geo_area" for which no system identifier could be generated
…=wp&search_word=ruth+mulvad&geo_area=')" target="_blank">Engkrogen 30 - 2860
✉
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 134, Column 138: entity was defined here
…query?what=wp&search_word=ruth+mulvad&geo_area=')" target="_blank">Engkrogen
