[Invalid] Markup Validation of http://metal3d.org/index.php/blog/ticket/2009/07/10/Quelques-liens-%C3%A0-partager

Errors found while checking this document as XHTML 1.0 Strict!

Result:	27 Errors, 15 warning(s)
Address:
Modified:	(undefined)
Server:	Apache/2.2.3 (CentOS)
Size:	(undefined)
Content-Type:	text/html
Encoding:	utf-8
Doctype:	XHTML 1.0 Strict
Root Element:	html
Root Namespace:	http://www.w3.org/1999/xhtml

Result:

27 Errors, 15 warning(s)

Address:

Modified:

(undefined)

Server:

Apache/2.2.3 (CentOS)

Size:

(undefined)

Content-Type:

text/html

Encoding:

utf-8

Doctype:

XHTML 1.0 Strict

Root Element:

html

Root Namespace:

http://www.w3.org/1999/xhtml

Options

Help on the options is available.

↑ Top

Validation Output: 27 Errors

Line 109, Column 13: element "g:plusone" undefined
```
		<g:plusone></g:plusone>
```
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
- by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
- by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 149, Column 19: there is no attribute "size"
```
		<g:plusone size="tall"></g:plusone>
```
✉

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. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 149, Column 25: element "g:plusone" undefined
```
		<g:plusone size="tall"></g:plusone>
```
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
- by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
- by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 532, Column 43: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
```
…       <div style="text-align:center;"><object width="200" height="300" classi…
```
✉

The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 532, Column 233: there is no attribute "align"
```
…sh/swflash.cab#version=7,0,0,0" align="middle"><param name="allowScriptAccess"…
```
✉

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. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 532, Column 412: cannot generate system identifier for general entity "playerautoplay"
```
….jamendo.com/fr/album/?album_id=80798&playerautoplay=0&playertype=2008&refuid=…
```
✉

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 532, Column 412: general entity "playerautoplay" not defined and no default entity
```
….jamendo.com/fr/album/?album_id=80798&playerautoplay=0&playertype=2008&refuid=…
```
✉

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 532, Column 426: reference not terminated by REFC delimiter
```
…r/album/?album_id=80798&playerautoplay=0&playertype=2008&refuid=41307" /><para…
```
✉

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 532, Column 426: reference to external entity in attribute value
```
…r/album/?album_id=80798&playerautoplay=0&playertype=2008&refuid=41307" /><para…
```
✉

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 '&'.
Line 532, Column 426: reference to entity "playerautoplay" for which no system identifier could be generated
```
…r/album/?album_id=80798&playerautoplay=0&playertype=2008&refuid=41307" /><para…
```
✉

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 532, Column 411: entity was defined here

…s.jamendo.com/fr/album/?album_id=80798&playerautoplay=0&playertype=2008&refuid…

Line 532, Column 429: cannot generate system identifier for general entity "playertype"
```
…lbum/?album_id=80798&playerautoplay=0&playertype=2008&refuid=41307" /><param n…
```
✉

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 532, Column 429: general entity "playertype" not defined and no default entity
```
…lbum/?album_id=80798&playerautoplay=0&playertype=2008&refuid=41307" /><param n…
```
✉

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 532, Column 439: reference not terminated by REFC delimiter
```
…m_id=80798&playerautoplay=0&playertype=2008&refuid=41307" /><param name="quali…
```
✉

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 532, Column 439: reference to external entity in attribute value
```
…m_id=80798&playerautoplay=0&playertype=2008&refuid=41307" /><param name="quali…
```
✉

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 '&'.
Line 532, Column 439: reference to entity "playertype" for which no system identifier could be generated
```
…m_id=80798&playerautoplay=0&playertype=2008&refuid=41307" /><param name="quali…
```
✉

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 532, Column 428: entity was defined here

…album/?album_id=80798&playerautoplay=0&playertype=2008&refuid=41307" /><param …

Line 532, Column 445: cannot generate system identifier for general entity "refuid"
```
…0798&playerautoplay=0&playertype=2008&refuid=41307" /><param name="quality" va…
```
✉

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 532, Column 445: general entity "refuid" not defined and no default entity
```
…0798&playerautoplay=0&playertype=2008&refuid=41307" /><param name="quality" va…
```
✉

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 532, Column 451: reference not terminated by REFC delimiter
```
…layerautoplay=0&playertype=2008&refuid=41307" /><param name="quality" value="h…
```
✉

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 532, Column 451: reference to external entity in attribute value
```
…layerautoplay=0&playertype=2008&refuid=41307" /><param name="quality" value="h…
```
✉

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 '&'.
Line 532, Column 451: reference to entity "refuid" for which no system identifier could be generated
```
…layerautoplay=0&playertype=2008&refuid=41307" /><param name="quality" value="h…
```
✉

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 532, Column 444: entity was defined here

…80798&playerautoplay=0&playertype=2008&refuid=41307" /><param name="quality" v…

Line 532, Column 549: there is no attribute "src"
```
…bgcolor" value="#FFFFFF" /><embed src="http://widgets.jamendo.com/fr/album/?al…
```
✉

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. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 532, Column 616: reference not terminated by REFC delimiter
```
…r/album/?album_id=80798&playerautoplay=0&playertype=2008&refuid=41307" quality…
```
✉

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 532, Column 616: reference to external entity in attribute value
```
…r/album/?album_id=80798&playerautoplay=0&playertype=2008&refuid=41307" quality…
```
✉

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 '&'.
Line 532, Column 616: reference to entity "playerautoplay" for which no system identifier could be generated
```
…r/album/?album_id=80798&playerautoplay=0&playertype=2008&refuid=41307" quality…
```
✉

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.