Markup Validation Service

Validation Output: 51 Errors

1. Line 154, Column 663: there is no attribute "size"

   … class="content"> <address><font size="1" color="#000000"></font></address><ad…

   ✉

   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.

2. Line 154, Column 673: there is no attribute "color"

   …ntent"> <address><font size="1" color="#000000"></font></address><address><fon…

   ✉

   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.

3. Line 154, Column 682: element "font" undefined

   …address><font size="1" color="#000000"></font></address><address><font size="1…

   ✉

   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).
4. Line 154, Column 739: element "font" undefined

   …ss><address><font size="1" color="#000000"></font></address><address></address>

   ✉

   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).
5. Line 157, Column 15: there is no attribute "width"

       <td width="100%" valign="top"><address><font size="1" color="#cc0000"><br /…

   ✉

   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.

6. Line 157, Column 74: element "font" undefined

   …address><font size="1" color="#cc0000"><br />Rua da Figueirinha, 2</font></add…

   ✉

   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).
7. Line 157, Column 158: element "font" undefined

   …address><font size="1" color="#cc0000">2425-617 Monte Redondo LRA</font></addr…

   ✉

   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).
8. Line 161, Column 74: element "font" undefined

   …address><font size="1" color="#cc0000"><span title="Call this phone number in …

   ✉

   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).
9. Line 161, Column 218: there is no attribute "skypeid"

   …id="softomate_v3_highlight_2" skypeid="2" skypeaction="call" fwidth=".w16" typ…

   ✉

   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.

10. Line 161, Column 234: there is no attribute "skypeaction"

    …_highlight_2" skypeid="2" skypeaction="call" fwidth=".w16" type=".flex" mode="…

    ✉

    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.

11. Line 161, Column 248: there is no attribute "fwidth"

    …skypeid="2" skypeaction="call" fwidth=".w16" type=".flex" mode=".compat" path=…

    ✉

    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.

12. Line 161, Column 260: there is no attribute "type"

    …skypeaction="call" fwidth=".w16" type=".flex" mode=".compat" path="file://C:/U…

    ✉

    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.

13. Line 161, Column 273: there is no attribute "mode"

    …call" fwidth=".w16" type=".flex" mode=".compat" path="file://C:/Users/HOLIVE~1…

    ✉

    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.

14. Line 161, Column 288: there is no attribute "path"

    …w16" type=".flex" mode=".compat" path="file://C:/Users/HOLIVE~1/AppData/Local/…

    ✉

    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.

15. Line 161, Column 409: there is no attribute "durex2"

    …a2ad4cdfd1daa2d0aad46/static/" durex2="%DADDYHEIGHT%" durex="%DADDYWIDTH%" con…

    ✉

    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.

16. Line 161, Column 431: there is no attribute "durex"

    …static/" durex2="%DADDYHEIGHT%" durex="%DADDYWIDTH%" context="244 689 040"><sp…

    ✉

    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.

17. Line 161, Column 454: there is no attribute "context"

    …HEIGHT%" durex="%DADDYWIDTH%" context="244 689 040"><span title="Skype actions…

    ✉

    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.

18. Line 161, Column 589: there is no attribute "skypesms"

    …ypeid="2" skypeaction="drop" skypesms="0"><span class="skype_v3_tb_imgFlag" id…

    ✉

    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.

19. Line 161, Column 1022: element "font" undefined

    …address><font size="1" color="#cc0000"><span title="Call this phone number in …

    ✉

    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).
20. Line 161, Column 2075: element "font" undefined

    …ail.pt"><font size="1" color="#cc0000"><br /></font></a></address><address><fo…

    ✉

    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).
21. Line 161, Column 2142: element "font" undefined

    …address><font size="1" color="#cc0000"></font></address><address><font size="1…

    ✉

    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).
22. Line 161, Column 2199: element "font" undefined

    …address><font size="1" color="#cc0000"></font></address><address><a href="http…

    ✉

    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).
23. Line 161, Column 2296: element "font" undefined

    ….80127986450073"><font color="#cc0000"><font size="1"></font></font></a></addr…

    ✉

    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).
24. Line 161, Column 2311: element "font" undefined

    …127986450073"><font color="#cc0000"><font size="1"></font></font></a></address>

    ✉

    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).
25. Line 165, Column 74: element "font" undefined

    …address><font size="1" color="#cc0000"><span class="nolink">Coordenadas GPS </…

    ✉

    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).
26. Line 165, Column 175: element "font" undefined

    …address><font size="1" color="#cc0000"><span class="nolink">N 30º 53' 43'' W 8…

    ✉

    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).
27. Line 165, Column 288: element "font" undefined

    …address><font size="1" color="#cc0000"><span class="nolink"><a title="Ver mapa…

    ✉

    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).
28. Line 165, Column 376: cannot generate system identifier for general entity "ie"

    …tp://maps.google.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018…

    ✉

    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.

29. Line 165, Column 376: general entity "ie" not defined and no default entity

    …tp://maps.google.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018…

    ✉

    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.

30. Line 165, Column 378: reference not terminated by REFC delimiter

    …://maps.google.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.0…

    ✉

    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.

31. Line 165, Column 378: reference to external entity in attribute value

    …://maps.google.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.0…

    ✉

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

32. Line 165, Column 378: reference to entity "ie" for which no system identifier could be generated

    …://maps.google.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.0…

    ✉

    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.

33. Line 165, Column 375: entity was defined here

    …ttp://maps.google.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=11182620766639218901…

34. Line 165, Column 384: cannot generate system identifier for general entity "msa"

    …s.google.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a2…

    ✉

    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.

35. Line 165, Column 384: general entity "msa" not defined and no default entity

    …s.google.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a2…

    ✉

    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.

36. Line 165, Column 387: reference not terminated by REFC delimiter

    …oogle.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a24c3…

    ✉

    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.

37. Line 165, Column 387: reference to external entity in attribute value

    …oogle.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a24c3…

    ✉

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

38. Line 165, Column 387: reference to entity "msa" for which no system identifier could be generated

    …oogle.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a24c3…

    ✉

    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.

39. Line 165, Column 383: entity was defined here

    …ps.google.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a…

40. Line 165, Column 390: cannot generate system identifier for general entity "msid"

    …le.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a24c3568…

    ✉

    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.

41. Line 165, Column 390: general entity "msid" not defined and no default entity

    …le.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a24c3568…

    ✉

    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.

42. Line 165, Column 394: reference not terminated by REFC delimiter

    …om/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a24c3568353f…

    ✉

    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.

43. Line 165, Column 394: reference to external entity in attribute value

    …om/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a24c3568353f…

    ✉

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

44. Line 165, Column 394: reference to entity "msid" for which no system identifier could be generated

    …om/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a24c3568353f…

    ✉

    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.

45. Line 165, Column 389: entity was defined here

    …gle.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a24c356…

46. Line 165, Column 439: cannot generate system identifier for general entity "ll"

    …207666392189018.00045a24c3568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.00…

    ✉

    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.

47. Line 165, Column 439: general entity "ll" not defined and no default entity

    …207666392189018.00045a24c3568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.00…

    ✉

    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.

48. Line 165, Column 441: reference not terminated by REFC delimiter

    …7666392189018.00045a24c3568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.0096…

    ✉

    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.

49. Line 165, Column 441: reference to external entity in attribute value

    …7666392189018.00045a24c3568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.0096…

    ✉

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

50. Line 165, Column 441: reference to entity "ll" for which no system identifier could be generated

    …7666392189018.00045a24c3568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.0096…

    ✉

    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.

51. Line 165, Column 438: entity was defined here

    …6207666392189018.00045a24c3568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.0…

52. Line 165, Column 462: cannot generate system identifier for general entity "spn"

    …4c3568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a2…

    ✉

    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.

53. Line 165, Column 462: general entity "spn" not defined and no default entity

    …4c3568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a2…

    ✉

    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.

54. Line 165, Column 465: reference not terminated by REFC delimiter

    …568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cc…

    ✉

    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.

55. Line 165, Column 465: reference to external entity in attribute value

    …568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cc…

    ✉

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

56. Line 165, Column 465: reference to entity "spn" for which no system identifier could be generated

    …568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cc…

    ✉

    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.

57. Line 165, Column 461: entity was defined here

    …24c3568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a…

58. Line 165, Column 484: cannot generate system identifier for general entity "z"

    …96592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target…

    ✉

    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.

59. Line 165, Column 484: general entity "z" not defined and no default entity

    …96592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target…

    ✉

    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.

60. Line 165, Column 485: reference not terminated by REFC delimiter

    …6592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target=…

    ✉

    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.

61. Line 165, Column 485: reference to external entity in attribute value

    …6592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target=…

    ✉

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

62. Line 165, Column 485: reference to entity "z" for which no system identifier could be generated

    …6592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target=…

    ✉

    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.

63. Line 165, Column 483: entity was defined here

    …896592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" targe…

64. Line 165, Column 489: cannot generate system identifier for general entity "iwloc"

    …,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target="_bl…

    ✉

    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.

65. Line 165, Column 489: general entity "iwloc" not defined and no default entity

    …,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target="_bl…

    ✉

    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.

66. Line 165, Column 494: reference not terminated by REFC delimiter

    …37074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target="_blank">…

    ✉

    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.

67. Line 165, Column 494: reference to external entity in attribute value

    …37074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target="_blank">…

    ✉

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

68. Line 165, Column 494: reference to entity "iwloc" for which no system identifier could be generated

    …37074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" 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.

69. Line 165, Column 488: entity was defined here

    …2,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target="_b…

70. Line 165, Column 525: there is no attribute "target"

    …7&iwloc=00045a24cce72f5d30a53" target="_blank">Clique para ver mapa</a></span>…

    ✉

    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.

71. Line 254, Column 52: element "font" undefined

    …e="text-align: left;">- <font size="1">Para alunos e Enc. de Educação</font><f…

    ✉

    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).
72. Line 254, Column 104: element "font" undefined

    …ont size="1">Para alunos e Enc. de Educação</font><font size="1">.</font></div>

    ✉

    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).
73. Line 255, Column 52: element "font" undefined

    …e="text-align: left;">- <font size="1">Na janela seguinte escolha &quot;Entrar…

    ✉

    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).
74. Line 255, Column 213: there is no attribute "vspace"

    …t/course/view.php?id=243"><img vspace="0" hspace="0" border="0" style="width: …

    ✉

    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.

75. Line 255, Column 224: there is no attribute "hspace"

    …ew.php?id=243"><img vspace="0" hspace="0" border="0" style="width: 222px; heig…

    ✉

    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.

76. Line 255, Column 235: there is no attribute "border"

    …43"><img vspace="0" hspace="0" border="0" style="width: 222px; height: 163px;"…

    ✉

    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.

77. Line 269, Column 195: required attribute "alt" not specified

    …c='http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/grupo_gps.png' border='0' /></a>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

78. Line 270, Column 136: required attribute "alt" not specified

    …='http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/logo-gpsef.png' border='0' /></a>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

79. Line 275, Column 7: end tag for "div" omitted, but OMITTAG NO was specified

    </body>

    ✉

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

80. Line 110, Column 1: start tag was here

    <div id="page">

↑ Top

Source Listing

Below is the source input I used for this validation:

1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2. <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="pt" xml:lang="pt">
3. <head>
4. <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
5. <link rel="stylesheet" type="text/css" href="http://moodle.cdlpc.pt/theme/standard/styles.php" />
6. <link rel="stylesheet" type="text/css" href="http://moodle.cdlpc.pt/theme/cdlpcm2010/styles.php" />
7. <meta name="description" content="" />
8. <!--[if IE 7]>
9. <link rel="stylesheet" type="text/css" href="http://moodle.cdlpc.pt/theme/standard/styles_ie7.css" />
10. <![endif]-->
11. <!--[if IE 6]>
12. <link rel="stylesheet" type="text/css" href="http://moodle.cdlpc.pt/theme/standard/styles_ie6.css" />
13. <![endif]-->
16. <meta name="keywords" content="moodle, Colégio Dr. Luís Pereira da Costa " />
17. <title>Colégio Dr. Luís Pereira da Costa</title>
18. <link rel="shortcut icon" href="http://moodle.cdlpc.pt/theme/cdlpcm2010/favicon.ico" />
19. <!--<style type="text/css">/*<![CDATA[*/ body{behavior:url(http://moodle.cdlpc.pt/lib/csshover.htc);} /*]]>*/</style>-->
21. <script type="text/javascript" src="http://moodle.cdlpc.pt/lib/javascript-static.js"></script>
22. <script type="text/javascript" src="http://moodle.cdlpc.pt/lib/javascript-mod.php"></script>
23. <script type="text/javascript" src="http://moodle.cdlpc.pt/lib/overlib/overlib.js"></script>
24. <script type="text/javascript" src="http://moodle.cdlpc.pt/lib/overlib/overlib_cssstyle.js"></script>
25. <script type="text/javascript" src="http://moodle.cdlpc.pt/lib/cookies.js"></script>
26. <script type="text/javascript" src="http://moodle.cdlpc.pt/lib/ufo.js"></script>
27. <script type="text/javascript" src="http://moodle.cdlpc.pt/lib/dropdown.js"></script>
29. <script type="text/javascript" defer="defer">
30. //<![CDATA[
31. setTimeout('fix_column_widths()', 20);
32. //]]>
33. </script>
34. <script type="text/javascript">
35. //<![CDATA[
36. function openpopup(url, name, options, fullscreen) {
37. var fullurl = "http://moodle.cdlpc.pt" + url;
38. var windowobj = window.open(fullurl, name, options);
39. if (!windowobj) {
40. return true;
41. }
42. if (fullscreen) {
43. windowobj.moveTo(0, 0);
44. windowobj.resizeTo(screen.availWidth, screen.availHeight);
45. }
46. windowobj.focus();
47. return false;
48. }
50. function uncheckall() {
51. var inputs = document.getElementsByTagName('input');
52. for(var i = 0; i < inputs.length; i++) {
53. inputs[i].checked = false;
54. }
55. }
57. function checkall() {
58. var inputs = document.getElementsByTagName('input');
59. for(var i = 0; i < inputs.length; i++) {
60. inputs[i].checked = true;
61. }
62. }
64. function inserttext(text) {
65. text = ' ' + text + ' ';
66. if ( opener.document.forms['theform'].message.createTextRange && opener.document.forms['theform'].message.caretPos) {
67. var caretPos = opener.document.forms['theform'].message.caretPos;
68. caretPos.text = caretPos.text.charAt(caretPos.text.length - 1) == ' ' ? text + ' ' : text;
69. } else {
70. opener.document.forms['theform'].message.value += text;
71. }
72. opener.document.forms['theform'].message.focus();
73. }
75. function getElementsByClassName(oElm, strTagName, oClassNames){
76. var arrElements = (strTagName == "*" && oElm.all)? oElm.all : oElm.getElementsByTagName(strTagName);
77. var arrReturnElements = new Array();
78. var arrRegExpClassNames = new Array();
79. if(typeof oClassNames == "object"){
80. for(var i=0; i<oClassNames.length; i++){
81. arrRegExpClassNames.push(new RegExp("(^|\\s)" + oClassNames[i].replace(/\-/g, "\\-") + "(\\s|$)"));
82. }
83. }
84. else{
85. arrRegExpClassNames.push(new RegExp("(^|\\s)" + oClassNames.replace(/\-/g, "\\-") + "(\\s|$)"));
86. }
87. var oElement;
88. var bMatchesAll;
89. for(var j=0; j<arrElements.length; j++){
90. oElement = arrElements[j];
91. bMatchesAll = true;
92. for(var k=0; k<arrRegExpClassNames.length; k++){
93. if(!arrRegExpClassNames[k].test(oElement.className)){
94. bMatchesAll = false;
95. break;
96. }
97. }
98. if(bMatchesAll){
99. arrReturnElements.push(oElement);
100. }
101. }
102. return (arrReturnElements)
103. }
104. //]]>
105. </script>
106. </head>
108. <body class="course course-1 notloggedin dir-ltr lang-pt_utf8" id="site-index">
110. <div id="page">
111. <a class="skip" href="#maincontent">Ir para o conteúdo principal</a>
113. <div id="header-home" class=" clearfix"> <!--<h1 class="headermain">Colégio Dr. Luís Pereira da Costa</h1>-->
115. </div> <div id="banner"><h1 class="headermain"></h1></div>
116. <div class="navbar clearfix">
117. <div class="breadcrumb"></div>
118. <div class="headermenu" style="color:White"><div class="logininfo">Utilizador não identificado. (<a href="http://moodle.cdlpc.pt/login/index.php">Entrar</a>)</div><form action="http://moodle.cdlpc.pt/course/jumpto.php" method="get" id="chooselang" class="popupform"><div><label for="chooselang_jump"><span class="accesshide " >Língua</span></label><select id="chooselang_jump" name="jump" onchange="self.location=document.getElementById('chooselang').jump.options[document.getElementById('chooselang').jump.selectedIndex].value;">
119. <option value="http://moodle.cdlpc.pt/index.php?lang=de_utf8">Deutsch (de)</option>
120. <option value="http://moodle.cdlpc.pt/index.php?lang=en_utf8">English (en)</option>
121. <option value="http://moodle.cdlpc.pt/index.php?lang=fr_utf8">Français (fr)</option>
122. <option value="http://moodle.cdlpc.pt/index.php?lang=pt_utf8" selected="selected">Português - Portugal (pt)</option>
123. </select><input type="hidden" name="sesskey" value="MIoDLOAuC4" /><div id="noscriptchooselang" style="display: inline;"><input type="submit" value="Executar" /></div><script type="text/javascript">
124. //<![CDATA[
125. document.getElementById("noscriptchooselang").style.display = "none";
126. //]]>
127. </script></div></form></div>
128. <div class="navbutton">&nbsp;</div>
129. </div>
130. <!-- END OF HEADER -->
131. <div id="content">
134. <table id="layout-table" summary="layout">
135. <tr>
136. <td style="width: 210px;" id="left-column"><div><a href="#sb-1" class="skip-block">Seguir para a frente de Grupos de disciplinas</a><div id="inst866" class="block_course_list sideblock"><div class="header"><div class="title"><input type="image" src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/t/switch_minus.gif" id="togglehide_inst866" onclick="elementToggleHide(this, true, function(el) {return findParentNode(el, 'DIV', 'sideblock'); }, 'Mostrar bloco Grupos de disciplinas', 'Esconder bloco Grupos de disciplinas'); return false;" alt="Esconder bloco Grupos de disciplinas" title="Esconder bloco Grupos de disciplinas" class="hide-show-image" /><h2>Grupos de disciplinas</h2></div></div><div class="content">
137. <ul class='list'>
138. <li class="r0"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=4">Direção</a></div></li>
139. <li class="r1"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=5">Sistema de Gestão da Qualidade</a></div></li>
140. <li class="r0"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=6">Direção de Turma</a></div></li>
141. <li class="r1"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=11">Departamentos</a></div></li>
142. <li class="r0"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=18">Ensino Profissional</a></div></li>
143. <li class="r1"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=35">SPO - Serviços de Psicologia e Orientação</a></div></li>
144. <li class="r0"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=85">Educação Especial</a></div></li>
145. <li class="r1"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=24">Secretariado de Exames</a></div></li>
146. <li class="r0"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=25">Avaliação de Desempenho de Professores</a></div></li>
147. <li class="r1"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=26">Recursos Humanos e Formação</a></div></li>
148. <li class="r0"><div class="icon column c0"><img src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/i/course.gif" class="icon" alt="Categoria da disciplina" /></div><div class="column c1"><a href="http://moodle.cdlpc.pt/course/category.php?id=87">Alunos</a></div></li>
149. </ul>
150. <div class="footer"><a href="http://moodle.cdlpc.pt/course/index.php">Todas as disciplinas</a> ...</div></div></div><script type="text/javascript">
151. //<![CDATA[
152. elementCookieHide("inst866","Mostrar bloco Grupos de disciplinas","Esconder bloco Grupos de disciplinas");
153. //]]>
154. </script><span id="sb-1" class="skip-block-to"></span><a href="#sb-2" class="skip-block">Seguir para a frente de Contactos</a><div id="inst874" class="block_html sideblock"><div class="header"><div class="title"><input type="image" src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/t/switch_minus.gif" id="togglehide_inst874" onclick="elementToggleHide(this, true, function(el) {return findParentNode(el, 'DIV', 'sideblock'); }, 'Mostrar bloco Contactos', 'Esconder bloco Contactos'); return false;" alt="Esconder bloco Contactos" title="Esconder bloco Contactos" class="hide-show-image" /><h2>Contactos</h2></div></div><div class="content"> <address><font size="1" color="#000000"></font></address><address><font size="1" color="#000000"></font></address><address></address>
155. <table rules="none" frame="void" cellspacing="10" cellpadding="1" border="0" width="198" style="background-image: none; border-style: none; text-align: left; width: 198px; height: 217px; vertical-align: top;"><tbody>
156. <tr>
157. <td width="100%" valign="top"><address><font size="1" color="#cc0000"><br />Rua da Figueirinha, 2</font></address><address><font size="1" color="#cc0000">2425-617 Monte Redondo LRA</font></address>
158. </td>
159. </tr>
160. <tr>
161. <td width="100%" valign="top"><address><font size="1" color="#cc0000"><span title="Call this phone number in Portugal with Skype: +351244689040" class="skype_v3_tb_injection" id="softomate_v3_highlight_2" skypeid="2" skypeaction="call" fwidth=".w16" type=".flex" mode=".compat" path="file://C:/Users/HOLIVE~1/AppData/Local/Temp/Low/__SkypeIEToolbar_Cache/18ec7742fdda2ad4cdfd1daa2d0aad46/static/" durex2="%DADDYHEIGHT%" durex="%DADDYWIDTH%" context="244 689 040"><span title="Skype actions" class="skype_v3_tb_imgA" id="skype_v3_tb_droppart_2" skypeid="2" skypeaction="drop" skypesms="0"><span class="skype_v3_tb_imgFlag" id="skype_v3_tb_img_f2"></span></span><span class="skype_v3_tb_imgS" id="skype_v3_tb_img_s2"></span><span class="skype_v3_tb_injectionIn" id="skype_v3_tb_text2"><span class="skype_v3_tb_innerText" id="skype_v3_tb_innerText2"> Tel: 244 689 040</span></span></span><span class="skype_v3_tb_injection_print" id="softomate_v3_print_2"></span> </font></address><address><font size="1" color="#cc0000"><span title="Call this phone number in Portugal with Skype: +351244689049" class="skype_v3_tb_injection" id="softomate_v3_highlight_3" skypeid="3" skypeaction="call" fwidth=".w16" type=".flex" mode=".compat" path="file://C:/Users/HOLIVE~1/AppData/Local/Temp/Low/__SkypeIEToolbar_Cache/18ec7742fdda2ad4cdfd1daa2d0aad46/static/" durex2="%DADDYHEIGHT%" durex="%DADDYWIDTH%" context="244 689 049"><span title="Skype actions" class="skype_v3_tb_imgA" id="skype_v3_tb_droppart_3" skypeid="3" skypeaction="drop" skypesms="0"><span class="skype_v3_tb_imgFlag" id="skype_v3_tb_img_f3"></span></span><span class="skype_v3_tb_imgS" id="skype_v3_tb_img_s3"></span><span class="skype_v3_tb_injectionIn" id="skype_v3_tb_text3"><span class="skype_v3_tb_innerText" id="skype_v3_tb_innerText3"> Fax: 244 689 049<br /><a href="mailto: geral@cdlpc.pt">geral@cdlpc.pt</a> </span></span></span><span class="skype_v3_tb_injection_print" id="softomate_v3_print_3"></span> </font></address><address><a href="mailto:col.luis.p.costa@sgps.mail.pt"><font size="1" color="#cc0000"><br /></font></a></address><address><font size="1" color="#cc0000"></font></address><address><font size="1" color="#cc0000"></font></address><address><a href="http://www.moodle.org/0.80127986450073"><font color="#cc0000"><font size="1"></font></font></a></address>
162. </td>
163. </tr>
164. <tr>
165. <td width="100%" valign="top"><address><font size="1" color="#cc0000"><span class="nolink">Coordenadas GPS </span></font></address><address><font size="1" color="#cc0000"><span class="nolink">N 30º 53' 43'' W 8º 50' 12''</span></font></address><address><font size="1" color="#cc0000"><span class="nolink"><a title="Ver mapa" href="http://maps.google.com/maps/ms?hl=pt-PT&ie=UTF8&msa=0&msid=111826207666392189018.00045a24c3568353fe0fa&ll=39.896592,-8.837074&spn=0.003976,0.009613&z=17&iwloc=00045a24cce72f5d30a53" target="_blank">Clique para ver mapa</a></span></font></address>
166. </td>
167. </tr></tbody>
168. </table><address></address></div></div><script type="text/javascript">
169. //<![CDATA[
170. elementCookieHide("inst874","Mostrar bloco Contactos","Esconder bloco Contactos");
171. //]]>
172. </script><span id="sb-2" class="skip-block-to"></span><a href="#sb-3" class="skip-block">Seguir para a frente de Calendário</a><div id="inst3988" class="block_calendar_month sideblock"><div class="header"><div class="title"><input type="image" src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/t/switch_minus.gif" id="togglehide_inst3988" onclick="elementToggleHide(this, true, function(el) {return findParentNode(el, 'DIV', 'sideblock'); }, 'Mostrar bloco Calendário', 'Esconder bloco Calendário'); return false;" alt="Esconder bloco Calendário" title="Esconder bloco Calendário" class="hide-show-image" /><h2>Calendário</h2></div></div><div class="content"><div id="overDiv" style="position: absolute; visibility: hidden; z-index:1000;"></div><script type="text/javascript" src="http://moodle.cdlpc.pt/calendar/overlib.cfg.php"></script>
173. <div class="calendar-controls"><a class="previous" href="index.php?cal_m=2&amp;cal_y=2020" title="Mês prévio"><span class="arrow ">&laquo;</span><span class="accesshide " >&nbsp;Mês prévio</span></a><span class="hide"> | </span><span class="current"><a href="http://moodle.cdlpc.pt/calendar/view.php?view=month&amp;course=1&amp;cal_d=1&amp;cal_m=03&amp;cal_y=2020">Março 2020</a></span><span class="hide"> | </span><a class="next" href="index.php?cal_m=4&amp;cal_y=2020" title="Próximo mês"><span class="accesshide " >Próximo mês&nbsp;</span><span class="arrow ">&raquo;</span></a>
174. <span class="clearer"><!-- --></span></div>
175. <table class="minicalendar" summary="Tabela de dados, Calendário de Março 2020"><tr class="weekdays"><th scope="col"><abbr title="Segunda">Seg</abbr></th>
176. <th scope="col"><abbr title="Terça">Ter</abbr></th>
177. <th scope="col"><abbr title="Quarta">Qua</abbr></th>
178. <th scope="col"><abbr title="Quinta">Qui</abbr></th>
179. <th scope="col"><abbr title="Sexta">Sex</abbr></th>
180. <th scope="col"><abbr title="Sábado">Sab</abbr></th>
181. <th scope="col"><abbr title="Domingo">Dom</abbr></th>
182. </tr><tr><td class="dayblank">&nbsp;</td>
183. <td class="dayblank">&nbsp;</td>
184. <td class="dayblank">&nbsp;</td>
185. <td class="dayblank">&nbsp;</td>
186. <td class="dayblank">&nbsp;</td>
187. <td class="dayblank">&nbsp;</td>
188. <td class="weekend day">1</td>
189. </tr><tr><td class="day">2</td>
190. <td class="day">3</td>
191. <td class="day">4</td>
192. <td class="day">5</td>
193. <td class="day">6</td>
194. <td class="weekend day">7</td>
195. <td class="weekend day">8</td>
196. </tr><tr><td class="day">9</td>
197. <td class="day">10</td>
198. <td class="day">11</td>
199. <td class="day">12</td>
200. <td class="day">13</td>
201. <td class="weekend day">14</td>
202. <td class="weekend day">15</td>
203. </tr><tr><td class="day">16</td>
204. <td class="day today eventnone"><span class="accesshide " >Hoje Terça, 17 Março </span><a href="#" onmouseover="return overlib('Sem eventos', CAPTION, 'Hoje Terça, 17 Março');" onmouseout="return nd();">17</a></td>
205. <td class="day">18</td>
206. <td class="day">19</td>
207. <td class="day">20</td>
208. <td class="weekend day">21</td>
209. <td class="weekend day">22</td>
210. </tr><tr><td class="day">23</td>
211. <td class="day">24</td>
212. <td class="day">25</td>
213. <td class="day">26</td>
214. <td class="day">27</td>
215. <td class="weekend day">28</td>
216. <td class="weekend day">29</td>
217. </tr><tr><td class="day">30</td>
218. <td class="day">31</td>
219. <td class="dayblank">&nbsp;</td><td class="dayblank">&nbsp;</td><td class="dayblank">&nbsp;</td><td class="dayblank">&nbsp;</td><td class="dayblank">&nbsp;</td></tr></table></div></div><script type="text/javascript">
220. //<![CDATA[
221. elementCookieHide("inst3988","Mostrar bloco Calendário","Esconder bloco Calendário");
222. //]]>
223. </script><span id="sb-3" class="skip-block-to"></span></div></td><td id="middle-column"><span id="maincontent"></span><div><h2 class="headingblock header ">Grupos de disciplinas</h2><div class="generalbox categorybox box">
225. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=4">Direção</a></td><td valign="top" class="category number">10</td></tr></table>
227. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=5">Sistema de Gestão da Qualidade</a></td><td valign="top" class="category number">1</td></tr></table>
229. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=6">Direção de Turma</a></td><td valign="top" class="category number"></td></tr></table>
231. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=11">Departamentos</a></td><td valign="top" class="category number"></td></tr></table>
233. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=18">Ensino Profissional</a></td><td valign="top" class="category number"></td></tr></table>
235. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=35">SPO - Serviços de Psicologia e Orientação</a></td><td valign="top" class="category number">4</td></tr></table>
237. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=85">Educação Especial</a></td><td valign="top" class="category number">1</td></tr></table>
239. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=24">Secretariado de Exames</a></td><td valign="top" class="category number">2</td></tr></table>
241. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=25">Avaliação de Desempenho de Professores</a></td><td valign="top" class="category number">1</td></tr></table>
243. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=26">Recursos Humanos e Formação</a></td><td valign="top" class="category number">1</td></tr></table>
245. <table class="categorylist"><tr><td valign="top" class="category name"><a href="http://moodle.cdlpc.pt/course/category.php?id=87">Alunos</a></td><td valign="top" class="category number"></td></tr></table></div><form id="coursesearch" action="http://moodle.cdlpc.pt/course/search.php" method="get"><fieldset class="coursesearchbox invisiblefieldset"><label for="shortsearchbox">Procurar disciplinas: </label><input type="text" id="shortsearchbox" size="12" name="search" alt="Procurar disciplinas" value="" /><input type="submit" value="Executar" /></fieldset></form><br /></div></td><td style="width: 180px;" id="right-column"><div><a href="#sb-4" class="skip-block">Seguir para a frente de Entrar</a><div id="inst4039" class="block_login sideblock"><div class="header"><div class="title"><input type="image" src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/t/switch_minus.gif" id="togglehide_inst4039" onclick="elementToggleHide(this, true, function(el) {return findParentNode(el, 'DIV', 'sideblock'); }, 'Mostrar bloco Entrar', 'Esconder bloco Entrar'); return false;" alt="Esconder bloco Entrar" title="Esconder bloco Entrar" class="hide-show-image" /><h2>Entrar</h2></div></div><div class="content">
246. <form class="loginform" id="login" method="post" action="http://moodle.cdlpc.pt/login/index.php"><div class="c1 fld username"><label for="login_username">Nome de utilizador</label><input type="text" name="username" id="login_username" value="" /></div><div class="c1 fld password"><label for="login_password">Senha</label><input type="password" name="password" id="login_password" value="" /></div><div class="c1 btn"><input type="submit" value="Entrar" /></div></form>
247. <div class="footer"><div><a href="http://moodle.cdlpc.pt/login/signup.php">Criar uma conta de utilizador!</a></div><div><a href="http://moodle.cdlpc.pt/login/forgot_password.php">recuperar senha</a></div></div></div></div><script type="text/javascript">
248. //<![CDATA[
249. elementCookieHide("inst4039","Mostrar bloco Entrar","Esconder bloco Entrar");
250. //]]>
251. </script><span id="sb-4" class="skip-block-to"></span><div id="inst2776" class="block_html sideblock"><div class="content">
252. <div style="text-align: center;"><a href="http://moodle.cdlpc.pt/course/view.php?id=243">INFORMAÇÕES SOBRE<br />EXAMES NACIONAIS</a><br />
253. <div style="text-align: center;">
254. <div style="text-align: left;">- <font size="1">Para alunos e Enc. de Educação</font><font size="1">.</font></div>
255. <div style="text-align: left;">- <font size="1">Na janela seguinte escolha &quot;Entrar como visitante&quot;.</font><br /></div><br /></div><a href="http://moodle.cdlpc.pt/course/view.php?id=243"><img vspace="0" hspace="0" border="0" style="width: 222px; height: 163px;" title="Informaçoes sobre Exames" alt="Informaçoes sobre Exames" src="http://moodle.cdlpc.pt/file.php/1/exames.jpg" /></a><br /></div>
256. <div style="text-align: center;"> </div></div></div><script type="text/javascript">
257. //<![CDATA[
258. elementCookieHide("inst2776","Mostrar bloco ","Esconder bloco ");
259. //]]>
260. </script><span id="sb-5" class="skip-block-to"></span><a href="#sb-6" class="skip-block">Seguir para a frente de Utilizadores activos</a><div id="inst873" class="block_online_users sideblock"><div class="header"><div class="title"><input type="image" src="http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/t/switch_minus.gif" id="togglehide_inst873" onclick="elementToggleHide(this, true, function(el) {return findParentNode(el, 'DIV', 'sideblock'); }, 'Mostrar bloco Utilizadores activos', 'Esconder bloco Utilizadores activos'); return false;" alt="Esconder bloco Utilizadores activos" title="Esconder bloco Utilizadores activos" class="hide-show-image" /><h2>Utilizadores activos</h2></div></div><div class="content"><div class="info">(nos últimos 30 minutos)</div><div class="info">Nenhum</div></div></div><script type="text/javascript">
261. //<![CDATA[
262. elementCookieHide("inst873","Mostrar bloco Utilizadores activos","Esconder bloco Utilizadores activos");
263. //]]>
264. </script><span id="sb-6" class="skip-block-to"></span></div></td>
265. </tr>
266. </table>
268. </div><div id="footer"><div style=" font-size:10px;font-family:Arial, Helvetica, sans-serif;color:#FFF"><a style="color:#FFF; text-decoration:underline" href="http://www.cdlpc.pt">Col&eacute;gio Dr. Lu&iacute;s Pereira da Costa</a> - Todos os direitos reservados &copy; 2010</div>
269. <div style="text-align:center; width:100%; vertical-align:top"><a target="_blank" href="http://www.grupogps.pt"><img src='http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/grupo_gps.png' border='0' /></a>
270. <a target="_blank" href="http://moodle.grupogps.pt"><img src='http://moodle.cdlpc.pt/theme/cdlpcm2010/pix/logo-gpsef.png' border='0' /></a>
271. </div>
273. </div>
275. </body>
276. </html>

↑ Top