5568 sujets

Sémantique web et HTML

[Resolu] Prb de validation XHTML à cause avec un lien externe ..

Bonjour,

J'ai ma DTD XHTML 1.0 Strict de ma page qui n'est pas valide à cause d'un lien extene vers la page de chargement du plgin flash, ce lien est dans un "p" d'un élément "Objet" qui lui même est dans un "div", si je supprime ce lien, ma page est validé mais si je le laisse j'ai plusieurs erreurs lors de la validation W3C dû à l'adresse du lien.
mon code de ma page :

  <div id="cLogBan"> <a href="index.html"><img src="../images/logo.gif" alt="commentaire" width="100" height="70" title="commentaire"/></a>
    <object type="application/x-shockwave-flash" data="../swf/pub.swf" width="649" height="80">
      <param name="play" value="true" />
      <param name="movie" value="../swf/pub.swf" />
      <param name="menu" value="false" />
      <param name="quality" value="high" />
      <param name="scalemode" value="noborder" />
      <p> OBJET FLASH NON AFFICHE, T&Egrave;L&Egrave;GARGER LE PLUGIN FLASH. CLIQUEZ SUR CE  
	  <a href="http://www.adobe.com/shockwave/download/index.cgi?Lang=French&P5_Language=French&P1_Prod_Version=ShockwaveFlash?Lang=French"/>LIEN</a>
	  </p>
	</object>
  </div>

Erreur validation W3C :
a écrit :

Result: Failed validation, 5 errors
File: essai.htm
Encoding: iso-8859-1
Doctype: XHTML 1.0 Strict
Root Namespace: http://www.w3.org/1999/xhtml

Note: The Validator XML support has some limitations.
This page is not Valid XHTML 1.0 Strict!

Below are the results of checking this document for XML well-formedness and validity.

1. Warning Line 26 column 74: cannot generate system identifier for general entity "P5_Language".

...kwave/download/index.cgi?Lang=French&P5_Language=French&P1_Prod_Version=Shock

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.

&#9993;
2. Error Line 26 column 74: general entity "P5_Language" not defined and no default entity.

...kwave/download/index.cgi?Lang=French&P5_Language=French&P1_Prod_Version=Shock

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.

&#9993;
3. Warning Line 26 column 85: reference not terminated by REFC delimiter.

...oad/index.cgi?Lang=French&P5_Language=French&P1_Prod_Version=ShockwaveFlash?L

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.

&#9993;
4. Warning Line 26 column 85: reference to external entity in attribute value.

...oad/index.cgi?Lang=French&P5_Language=French&P1_Prod_Version=ShockwaveFlash?L

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;'.

&#9993;
5. Error Line 26 column 85: reference to entity "P5_Language" for which no system identifier could be generated.

...oad/index.cgi?Lang=French&P5_Language=French&P1_Prod_Version=ShockwaveFlash?L

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.

&#9993;
6. Info Line 26 column 73: entity was defined here.

...ckwave/download/index.cgi?Lang=French&P5_Language=French&P1_Prod_Version=Shoc

7. Warning Line 26 column 93: cannot generate system identifier for general entity "P1_Prod_Version".

...x.cgi?Lang=French&P5_Language=French&P1_Prod_Version=ShockwaveFlash?Lang=Fren

&#9993;
8. Error Line 26 column 93: general entity "P1_Prod_Version" not defined and no default entity.

...x.cgi?Lang=French&P5_Language=French&P1_Prod_Version=ShockwaveFlash?Lang=Fren

&#9993;
9. Warning Line 26 column 108: reference not terminated by REFC delimiter.

...ch&P5_Language=French&P1_Prod_Version=ShockwaveFlash?Lang=French"/>LIEN</a>

&#9993;
10. Warning Line 26 column 108: reference to external entity in attribute value.

...ch&P5_Language=French&P1_Prod_Version=ShockwaveFlash?Lang=French"/>LIEN</a>

&#9993;
11. Error Line 26 column 108: reference to entity "P1_Prod_Version" for which no system identifier could be generated.

...ch&P5_Language=French&P1_Prod_Version=ShockwaveFlash?Lang=French"/>LIEN</a>

&#9993;
12. Info Line 26 column 92: entity was defined here.

...ex.cgi?Lang=French&P5_Language=French&P1_Prod_Version=ShockwaveFlash?Lang=Fre

13. Error Line 26 column 145: end tag for element "a" which is not open.

...=ShockwaveFlash?Lang=French"/>LIEN</a>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occured in a script section of your document, you should probably read this FAQ entry.


Merci de vos lumières ...
Modifié par Gobelin (04 Aug 2006 - 13:57)
Sujet clos
Aller à