This page is not Valid XHTML 1.0 Transitional!

Result: Failed validation, 40 Errors
:
: iso-8859-1
: XHTML 1.0 Transitional
Root Element: html
Root Namespace: http://www.w3.org/1999/xhtml
Options

Help on the options is available.

↑ Top

Validation Output: 40 Errors

  1. Warning Line 29, Column 90: character "<" is the first character of a delimiter but occurred as data.
    …ER POP &amp; Gauche en mouvement</a> <<<</strong><br />

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  2. Warning Line 29, Column 91: character "<" is the first character of a delimiter but occurred as data.
    …R POP &amp; Gauche en mouvement</a> <<<</strong><br />

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  3. Warning Line 29, Column 92: character "<" is the first character of a delimiter but occurred as data.
    … POP &amp; Gauche en mouvement</a> <<<</strong><br />

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  4. Warning Line 323, Column 76: character "&" is the first character of a delimiter but occurred as data.
    …ces publiques des &eacute;lu-e-s POP & Gauche en Mouvement">Permanences publi

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  5. Warning Line 324, Column 23: cannot generate system identifier for general entity "more".
    	  <li><a href="?p=277&more=1" title="Les &eacute;luEs">Les &eacute;luEs</a></…

    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.

  6. Error Line 324, Column 23: general entity "more" not defined and no default entity.
    	  <li><a href="?p=277&more=1" title="Les &eacute;luEs">Les &eacute;luEs</a></…

    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.

  7. Warning Line 324, Column 27: reference not terminated by REFC delimiter.
    	  <li><a href="?p=277&more=1" title="Les &eacute;luEs">Les &eacute;luEs</a></…

    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.

  8. Warning Line 324, Column 27: reference to external entity in attribute value.
    	  <li><a href="?p=277&more=1" title="Les &eacute;luEs">Les &eacute;luEs</a></…

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

  9. Error Line 324, Column 27: reference to entity "more" for which no system identifier could be generated.
    	  <li><a href="?p=277&more=1" title="Les &eacute;luEs">Les &eacute;luEs</a></…

    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.

  10. Info Line 324, Column 22: entity was defined here.
    	  <li><a href="?p=277&more=1" title="Les &eacute;luEs">Les &eacute;luEs</a></…
  11. Warning Line 335, Column 26: reference not terminated by REFC delimiter.
    	  <li><a href="?p=26&more=1" title="Comment adh&eacute;rer ?">Comment adh&eacut

    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.

  12. Warning Line 335, Column 26: reference to external entity in attribute value.
    	  <li><a href="?p=26&more=1" title="Comment adh&eacute;rer ?">Comment adh&eacut

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

  13. Error Line 335, Column 26: reference to entity "more" for which no system identifier could be generated.
    	  <li><a href="?p=26&more=1" title="Comment adh&eacute;rer ?">Comment adh&eacut

    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.

  14. Info Line 324, Column 22: entity was defined here.
    	  <li><a href="?p=277&more=1" title="Les &eacute;luEs">Les &eacute;luEs</a></…
  15. Warning Line 336, Column 27: reference not terminated by REFC delimiter.
    	  <li><a href="?p=245&more=1" title="Recevoir des infos">Recevoir des infos</a>

    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.

  16. Warning Line 336, Column 27: reference to external entity in attribute value.
    	  <li><a href="?p=245&more=1" title="Recevoir des infos">Recevoir des infos</a>

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

  17. Error Line 336, Column 27: reference to entity "more" for which no system identifier could be generated.
    	  <li><a href="?p=245&more=1" title="Recevoir des infos">Recevoir des infos</a>

    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.

  18. Info Line 324, Column 22: entity was defined here.
    	  <li><a href="?p=277&more=1" title="Les &eacute;luEs">Les &eacute;luEs</a></…
  19. Error Line 346, Column 158: end tag for "img" omitted, but OMITTAG NO was specified.
    …g" border="0" alt="Po&egrave;sie"></a><br />

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  20. Info Line 346, Column 66: start tag was here.
    …cute;sie du mois">Po&eacute;sie<br /><img src="/images/resistance/poesie_Mart
  21. Error Line 350, Column 156: end tag for "img" omitted, but OMITTAG NO was specified.
    …jpg" border="0" alt="Gourmandise"></a><br />

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  22. Info Line 350, Column 72: start tag was here.
    …mois">Plat de R&eacute;sistance<br /><img src="/images/resistance/platR_Porto
  23. Error Line 354, Column 169: end tag for "img" omitted, but OMITTAG NO was specified.
    …er="0" alt="Georges Taffelmacher"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  24. Info Line 354, Column 64: start tag was here.
    …trait du mois">Portrait du mois<br /><img src="/images/resistance/portrait_Ge
  25. Error Line 396, Column 11: ID "logo" already defined.
      <div id="logo">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  26. Info Line 283, Column 10: ID "logo" first defined here.
    	<div id="logo">
  27. Error Line 436, Column 9: ID "newmenu" already defined.
    <div id="newmenu">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  28. Info Line 319, Column 10: ID "newmenu" first defined here.
    	<div id="newmenu">
  29. Error Line 455, Column 9: ID "newmenu" already defined.
    <div id="newmenu">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  30. Info Line 319, Column 10: ID "newmenu" first defined here.
    	<div id="newmenu">
  31. Error Line 477, Column 9: ID "newmenu" already defined.
    <div id="newmenu">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  32. Info Line 319, Column 10: ID "newmenu" first defined here.
    	<div id="newmenu">
  33. Error Line 489, Column 9: ID "newmenu" already defined.
    <div id="newmenu">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  34. Info Line 319, Column 10: ID "newmenu" first defined here.
    	<div id="newmenu">
  35. Error Line 547, Column 141: end tag for "img" omitted, but OMITTAG NO was specified.
    …ep.png" alt="European Left Party"></a><br />

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  36. Info Line 547, Column 85: start tag was here.
    …European Left Party" target="_blank"><img src="/images/lep.png" alt="European
  37. Error Line 550, Column 69: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.
    …tle="Parti Suisse du Travail" target=_blank>Parti Suisse du Travail</a><br />

  38. Error Line 551, Column 94: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.
    …darit&eacute;s Gen&egrave;ve" target=_blank>solidarit&eacute;S</a><br />

  39. Error Line 29, Column > 80: XML Parsing Error: StartTag: invalid element name.
    …grave; VOTER POP &amp; Gauche en mouvement</a> <<<</strong><br />…

  40. Error Line 29, Column > 80: XML Parsing Error: StartTag: invalid element name.
    …grave; VOTER POP &amp; Gauche en mouvement</a> <<<</strong><br />…

  41. Error Line 29, Column > 80: XML Parsing Error: StartTag: invalid element name.
    …grave; VOTER POP &amp; Gauche en mouvement</a> <<<</strong><br />…

  42. Error Line 323, Column 77: XML Parsing Error: xmlParseEntityRef: no name.
    …es publiques des &eacute;lu-e-s POP & Gauche en Mouvement">Permanences publiq

  43. Error Line 324, Column 27: XML Parsing Error: EntityRef: expecting ';'.
    	  <li><a href="?p=277&more=1" title="Les &eacute;luEs">Les &eacute;luEs</a></…

  44. Error Line 335, Column 26: XML Parsing Error: EntityRef: expecting ';'.
    	  <li><a href="?p=26&more=1" title="Comment adh&eacute;rer ?">Comment adh&eacut

  45. Error Line 336, Column 27: XML Parsing Error: EntityRef: expecting ';'.
    	  <li><a href="?p=245&more=1" title="Recevoir des infos">Recevoir des infos</a>

  46. Error Line 346, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 346 and a.
    …is">Po&eacute;sie<br /><img src="/images/resistance/poesie_Martin_Niemoller.j…

  47. Error Line 350, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 350 and a.
    …at de R&eacute;sistance<br /><img src="/images/resistance/platR_PortoNovo_m.j…

  48. Error Line 354, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 354 and a.
    …ortrait du mois<br /><img src="/images/resistance/portrait_Georges_Taffelmach…

  49. Error Line 392, Column 6: XML Parsing Error: Opening and ending tag mismatch: a line 354 and div.
    </div>

  50. Error Line 547, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 547 and a.
    …tle="European Left Party" target="_blank"><img src="/images/lep.png" alt="Eur…

  51. Error Line 550, Column 69: XML Parsing Error: AttValue: " or ' expected.
    …tle="Parti Suisse du Travail" target=_blank>Parti Suisse du Travail</a><br />

  52. Error Line 550, Column 69: XML Parsing Error: attributes construct error.
    …tle="Parti Suisse du Travail" target=_blank>Parti Suisse du Travail</a><br />

  53. Error Line 550, Column 69: XML Parsing Error: Couldn't find end of Start Tag a line 550.
    …tle="Parti Suisse du Travail" target=_blank>Parti Suisse du Travail</a><br />

  54. Error Line 551, Column > 80: XML Parsing Error: AttValue: " or ' expected.
    …/" title="Solidarit&eacute;s Gen&egrave;ve" target=_blank>solidarit&eacute;S<…

  55. Error Line 551, Column > 80: XML Parsing Error: attributes construct error.
    …/" title="Solidarit&eacute;s Gen&egrave;ve" target=_blank>solidarit&eacute;S<…

  56. Error Line 551, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 551.
    …/" title="Solidarit&eacute;s Gen&egrave;ve" target=_blank>solidarit&eacute;S<…

  57. Error Line 551, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 394 and a.
    …/" title="Solidarit&eacute;s Gen&egrave;ve" target=_blank>solidarit&eacute;S<…

  58. Error Line 568, Column 6: XML Parsing Error: Opening and ending tag mismatch: a line 350 and div.
    </div>

  59. Error Line 569, Column 6: XML Parsing Error: Opening and ending tag mismatch: a line 346 and div.
    </div>

  60. Error Line 570, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 282 and body.
    </body>

  61. Error Line 571, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 24 and html.
    </html>

  62. Error Line 571, Column 7: XML Parsing Error: Premature end of data in tag body line 23.
    </html>

  63. Error Line 571, Column 7: XML Parsing Error: Premature end of data in tag html line 3.
    </html>

↑ Top