lostinfr
08-01-2005, 07:33 AM
Hello,
I'm trying to validate one of my pages, I've managed to fix everything except these 2 which I don't understand.
XHTML 1.0 Transitional
(1) (I've put '<' so the html doesn't mess up this post)
Line 27, column 46: there is no attribute "background"
'<'td align="center" background="images/top_tab_bg.gif" alt="bgound" wid
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute.
(2) Short of just getting rid of the link I'm stuck as to how I change it to please the validation :)
Line 101, column 159: cannot generate system identifier for general entity "Niveau"
...me_interrogation.asp?ACTION=nouvelle&Niveau=siren">
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.
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.
I'm trying to validate one of my pages, I've managed to fix everything except these 2 which I don't understand.
XHTML 1.0 Transitional
(1) (I've put '<' so the html doesn't mess up this post)
Line 27, column 46: there is no attribute "background"
'<'td align="center" background="images/top_tab_bg.gif" alt="bgound" wid
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute.
(2) Short of just getting rid of the link I'm stuck as to how I change it to please the validation :)
Line 101, column 159: cannot generate system identifier for general entity "Niveau"
...me_interrogation.asp?ACTION=nouvelle&Niveau=siren">
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.
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.