# Markup Validation Service

Check the markup (HTML, XHTML, …) of Web documents

## Errors found while checking this document as XHTML 1.0 Strict!

Result: | 441 Errors, 42 warning(s)
Address: |
Encoding: | utf-8 |
Doctype: | XHTML 1.0 Strict |
Root Element: | html
Root Namespace: | http://www.w3.org/1999/xhtml

Options

Show Source | Show Outline | List Messages Sequentially Group Error Messages by Type
Validate error pages | Verbose Output | Clean up Markup with HTML Tidy

Help on the options is available.

↑ Top

### Validation Output: 441 Errors

1. Line 24, Column 47: end tag for "meta" omitted, but OMITTAG NO was specified

       …="y_key" content="1d8b62e6da1997a…

   ✉

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

2. Line 24: start tag was here

       ><meta name="y_key" content="1d8b62e6da1997ab">

3. Line 169, Column 299: character "&amp;" is the first character of a delimiter but occurred as data

       …type="text/javascript">    if (!nad && typeof(window["GS_googleAddAdSenseServ

   ✉

   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. Line 169, Column 300: character "&amp;" is the first character of a delimiter but occurred as data

       …ype="text/javascript">    if (!nad && typeof(window["GS_googleAddAdSenseServi

   ✉

   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. Line 244, Column 31: an attribute value must be a literal unless it contains only name characters

       document.writeln('<style type=\"text/css\">');

   ✉

   You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

6. Line 244, Column 43: document type does not allow element "style" here

       document.writeln('<style type=\"text/css\">');

   ✉

   The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

   One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

7. Line 328, Column 71: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

       …" class="txt" type="text" value="" /> <a onclick="if ($('#txt_searchBox')[0].

   ✉

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

   One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

8. Line 328, Column 187: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

       …('#fm_Search').submit();};" href="#"><img alt="Search" src="/gfx/00/07/40/bt-

   ✉

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

   One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

9. Line 1012, Column 82: character "&amp;" is the first character of a delimiter but occurred as data

       …chedule---results/" title="Schedule & Results">Schedule & Results</a></li>

   ✉

   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.
10. Line 1012, Column 102: character "&amp;" is the first character of a delimiter but occurred as data

        …title="Schedule & Results">Schedule & Results</a></li>

    ✉

    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.
11. Line 1116, Column 20: Attribute "language" exists, but can not be used for this element.

        		<script language="JavaScript" type="text/javascript">

    ✉

    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 1123, Column 28: an attribute value must be a literal unless it contains only name characters

        document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

    ✉

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

13. Line 1123, Column 57: "height:" is not a member of a group specified for any attribute

        … style=\"position:relative; height: 293px;\"><div style=\"position:absolute;

    ✉

14. Line 1123, Column 57: "293px" is not a member of a group specified for any attribute

        … style=\"position:relative; height: 293px;\"><div style=\"position:absolute;

    ✉

15. Line 1123, Column 65: document type does not allow element "div" here

        …"position:relative; height: 293px;\"><div style=\"position:absolute; left: -1

    ✉

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

16. Line 1123, Column 77: an attribute value must be a literal unless it contains only name characters

        …:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

    ✉

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

17. Line 1123, Column 104: "left:" is not a member of a group specified for any attribute

        …iv style=\"position:absolute; left: -19px;\">");

    ✉

18. Line 1123, Column 104: "-19px" is not a member of a group specified for any attribute

        …iv style=\"position:absolute; left: -19px;\">");

    ✉

19. Line 1219, Column 187: required attribute "alt" not specified

        …/27/51/96580441_36imgGalTh-TT.jpg" />

    ✉

    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>`.

20. Line 1260, Column 164: required attribute "alt" not specified

        …/27/72/96675153_76imgGalTh-tX.jpg" />

    ✉

    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>`.

21. Line 1301, Column 175: required attribute "alt" not specified

        …/27/69/96669004_82imgGalTh-FI.jpg" />

    ✉

    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>`.

22. Line 1394, Column 229: required attribute "alt" not specified

        …/27/75/96689541_34imgGalTh-NK.jpg" />

    ✉

    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>`.

23. Line 1403, Column 225: required attribute "alt" not specified

        …/27/75/96689347_36imgGalTh-SM.jpg" />

    ✉

    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>`.

24. Line 1412, Column 231: required attribute "alt" not specified

        …/27/75/96689148_30imgGalTh-GV.jpg" />

    ✉

    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>`.

25. Line 1421, Column 233: required attribute "alt" not specified

        …/27/75/96689498_28imgGalTh-jQ.jpg" />

    ✉

    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>`.

26. Line 1430, Column 219: required attribute "alt" not specified

        …/27/75/96689415_26imgGalTh-KX.jpg" />

    ✉

    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>`.

27. Line 1439, Column 217: required attribute "alt" not specified

        …/27/75/96689267_22imgGalTh-SY.jpg" />

    ✉

    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>`.

28. Line 1458, Column 215: required attribute "alt" not specified

        …/27/75/96689285_20imgGalTh-Eu.jpg" />

    ✉

    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>`.

29. Line 1467, Column 209: required attribute "alt" not specified

        …/27/75/96689361_18imgGalTh-CI.jpg" />

    ✉

    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>`.

30. Line 1476, Column 229: required attribute "alt" not specified

        …/27/75/96689125_16imgGalTh-NY.jpg" />

    ✉

    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>`.

31. Line 1485, Column 223: required attribute "alt" not specified

        …/27/75/96689149_14imgGalTh-YA.jpg" />

    ✉

    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>`.

32. Line 1494, Column 225: required attribute "alt" not specified

        …/27/75/96689203_12imgGalTh-dB.jpg" />

    ✉

    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>`.

33. Line 1503, Column 205: required attribute "alt" not specified

        …/27/75/94919020_00imgGalTh-Gx.jpg" />

    ✉

    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>`.

34. Line 1522, Column 207: required attribute "alt" not specified

        …/27/74/56929574_90imgGalTh-Dy.jpg" />

    ✉

    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>`.

35. Line 1531, Column 141: required attribute "alt" not specified

        …/27/73/96675801_90imgGalTh-LM.jpg" />

    ✉

    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>`.

36. Line 1540, Column 197: required attribute "alt" not specified

        …/27/72/96675364_90imgGalTh-TP.jpg" />

    ✉

    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>`.

37. Line 1549, Column 205: required attribute "alt" not specified

        …/27/72/96672881_92imgGalTh-uW.jpg" />

    ✉

    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>`.

38. Line 1558, Column 197: required attribute "alt" not specified

        …/27/72/96667497_94imgGalTh-Fz.jpg" />

    ✉

    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>`.

39. Line 1567, Column 193: required attribute "alt" not specified

        …/27/72/96672170_96imgGalTh-GB.jpg" />

    ✉

    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>`.

40. Line 1586, Column 203: required attribute "alt" not specified

        …/27/72/96672048_88imgGalTh-TS.jpg" />

    ✉

    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>`.

41. Line 1595, Column 261: required attribute "alt" not specified

        …/27/72/96675307_86imgGalTh-Qd.jpg" />

    ✉

    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>`.

42. Line 1604, Column 247: required attribute "alt" not specified

        …/27/72/96670316_82imgGalTh-Ho.jpg" />

    ✉

    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>`.

43. Line 1613, Column 215: required attribute "alt" not specified

        …/27/72/96675422_84imgGalTh-Td.jpg" />

    ✉

    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>`.

44. Line 1622, Column 331: required attribute "alt" not specified

        …/27/72/96675153_76imgGalTh-tX.jpg" />

    ✉

    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>`.

45. Line 1631, Column 277: required attribute "alt" not specified

        …/27/72/96674975_74imgGalTh-cE.jpg" />

    ✉

    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>`.

46. Line 1650, Column 261: required attribute "alt" not specified

        …/27/72/96674760_72imgGalTh-AK.jpg" />

    ✉

    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>`.

47. Line 1659, Column 237: required attribute "alt" not specified

        …/27/72/96673251_14imgGalTh-Rc.jpg" />

    ✉

    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>`.

48. Line 1668, Column 253: required attribute "alt" not specified

        …/27/70/96669544_88imgGalTh-uL.jpg" />

    ✉

    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>`.

49. Line 1677, Column 235: required attribute "alt" not specified

        …/27/70/96669535_80imgGalTh-lH.jpg" />

    ✉

    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>`.

50. Line 1686, Column 251: required attribute "alt" not specified

        …/27/70/96669402_78imgGalTh-Qr.jpg" />

    ✉

    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>`.

51. Line 1695, Column 285: required attribute "alt" not specified

        …/27/70/96669399_76imgGalTh-VE.jpg" />

    ✉

    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>`.

52. Line 1753, Column 140: cannot generate system identifier for general entity "utm_medium"

        …1.html?utm_campaign=openingceremony&utm_medium=opening&utm_source=banneren&ut

    ✉

    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 1753, Column 140: general entity "utm_medium" not defined and no default entity

        …1.html?utm_campaign=openingceremony&utm_medium=opening&utm_source=banneren&ut

    ✉

    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 1753, Column 150: reference not terminated by REFC delimiter

        …_campaign=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=

    ✉

    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 1753, Column 150: reference to external entity in attribute value

        …_campaign=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=

    ✉

    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 1753, Column 150: reference to entity "utm_medium" for which no system identifier could be generated

        …_campaign=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=

    ✉

    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 1753, Column 138: entity was defined here

        …-p1.html?utm_campaign=openingceremony&utm_medium=opening&utm_source=banneren&

58. Line 1753, Column 159: cannot generate system identifier for general entity "utm_source"

        …=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=openingrn

    ✉

    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 1753, Column 159: general entity "utm_source" not defined and no default entity

        …=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=openingrn

    ✉

    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 1753, Column 169: reference not terminated by REFC delimiter

        …remony&utm_medium=opening&utm_source=banneren&utm_content=openingrn" title="L

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

61. Line 1753, Column 169: reference to external entity in attribute value

        …remony&utm_medium=opening&utm_source=banneren&utm_content=openingrn" title="L

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

62. Line 1753, Column 169: reference to entity "utm_source" for which no system identifier could be generated

        …remony&utm_medium=opening&utm_source=banneren&utm_content=openingrn" title="L

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

63. Line 1753, Column 157: entity was defined here

        …gn=openingceremony&utm_medium=opening&utm_source=banneren&utm_content=opening

64. Line 1753, Column 179: cannot generate system identifier for general entity "utm_content"

        …_medium=opening&utm_source=banneren&utm_content=openingrn" title="Let the Gam

    ✉

    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 1753, Column 179: general entity "utm_content" not defined and no default entity

        …_medium=opening&utm_source=banneren&utm_content=openingrn" title="Let the Gam

    ✉

    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 1753, Column 190: reference not terminated by REFC delimiter

        …ning&utm_source=banneren&utm_content=openingrn" title="Let the Games Begin!">

    ✉

    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 1753, Column 190: reference to external entity in attribute value

        …ning&utm_source=banneren&utm_content=openingrn" title="Let the Games Begin!">

    ✉

    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 1753, Column 190: reference to entity "utm_content" for which no system identifier could be generated

        …ning&utm_source=banneren&utm_content=openingrn" title="Let the Games Begin!">

    ✉

    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 1753, Column 177: entity was defined here

        …tm_medium=opening&utm_source=banneren&utm_content=openingrn" title="Let the G

70. Line 1753, Column 299: required attribute "alt" not specified

        …mepage-souvenirprogram_64d-hz.jpg" /></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>`.

71. Line 1778, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

    ✉

    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.
72. Line 1778, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

    ✉

    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.
73. Line 1850, Column 232: required attribute "alt" not specified

        …packed-olympics_10imgGalTh-nV.jpg" />

    ✉

    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>`.

74. Line 1896, Column 166: required attribute "alt" not specified

        …ideo--8---day-3_34imgGalTh-TJ.jpg" />

    ✉

    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>`.

75. Line 1942, Column 166: required attribute "alt" not specified

        …ideo--7---day-2_28imgGalTh-Jx.jpg" />

    ✉

    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>`.

76. Line 2033, Column 107: required attribute "alt" not specified

        …0/09/57/culture_42imgGalTh-ch.jpg" />

    ✉

    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>`.

77. Line 2069, Column 158: required attribute "alt" not specified

        …g/00/09/57/code_46imgGalTh-bA.jpg" />

    ✉

    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 2114, Column 183: required attribute "alt" not specified

        …0/27/32/live-55_60imgGalTh-Zp.jpg" />

    ✉

    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 2172, Column 353: required attribute "alt" not specified

        …vertical-align:middle !important;" /> Vancouver 2010 </a><br /><a href="http:

    ✉

    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>`.

80. Line 2172, Column 542: required attribute "alt" not specified

        …vertical-align:middle !important;" /> Cultural Olympiad</a></div>

    ✉

    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>`.

81. Line 2173, Column 300: required attribute "alt" not specified

        …vertical-align:middle !important;" /> Vancouver 2010</a><br />

    ✉

    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>`.

82. Line 2174, Column 148: required attribute "alt" not specified

        …vertical-align:middle !important;" /> Torch Relay</a><br />

    ✉

    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>`.

83. Line 2175, Column 142: required attribute "alt" not specified

        …vertical-align:middle !important;" /> CODE 2010</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>`.

84. Line 2200, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

    ✉

    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.
85. Line 2200, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

    ✉

    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.
86. Line 2314, Column 17: ID "x" already defined

        								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    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).

87. Line 2280, Column 17: ID "x" first defined here

                 <tr id="x">

88. Line 2328, Column 17: ID "x" already defined

        								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    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).

89. Line 2280, Column 17: ID "x" first defined here

                 <tr id="x">

90. Line 2342, Column 17: ID "x" already defined

        								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    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).

91. Line 2280, Column 17: ID "x" first defined here

                 <tr id="x">

92. Line 2356, Column 17: ID "x" already defined

        								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    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).

93. Line 2280, Column 17: ID "x" first defined here

                 <tr id="x">

94. Line 2370, Column 17: ID "x" already defined

        								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    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).

95. Line 2280, Column 17: ID "x" first defined here

                 <tr id="x">

96. Line 2384, Column 17: ID "x" already defined

        								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    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).

97. Line 2280, Column 17: ID "x" first defined here

                 <tr id="x">

98. Line 2398, Column 17: ID "x" already defined

        								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    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).

99. Line 2280, Column 17: ID "x" first defined here

                 <tr id="x">

100. Line 2412, Column 17: ID "x" already defined

         								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     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).

101. Line 2280, Column 17: ID "x" first defined here

                  <tr id="x">

102. Line 2426, Column 17: ID "x" already defined

         								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     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).

103. Line 2280, Column 17: ID "x" first defined here

                  <tr id="x">

104. Line 2440, Column 17: ID "x" already defined

         								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     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).

105. Line 2280, Column 17: ID "x" first defined here

                  <tr id="x">

106. Line 2463, Column 17: ID "x" already defined

         								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     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).

107. Line 2280, Column 17: ID "x" first defined here

                  <tr id="x">

108. Line 2494, Column 120: Attribute "target" exists, but can not be used for this element.

         …this widget on your website" target="_top"><img src="/gfx/00/27/06/widgetmeda

     ✉

     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.

109. Line 2494, Column 182: required attribute "alt" not specified

         …7/06/widgetmedalsembed_86d-JB.gif" /></a></span>

     ✉

     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>`.

110. Line 2532, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

           if (!(typeof nad === "undefined") && !nad)

     ✉

     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.
111. Line 2532, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

           if (!(typeof nad === "undefined") && !nad)

     ✉

     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.
112. Line 2557, Column 9: required attribute "type" not specified

         		<style>

     ✉

     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>`.

113. Line 2557, Column 9: document type does not allow element "style" here

         		<style>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

114. Line 2565, Column 12: Attribute "name" exists, but can not be used for this element.

         <form name="#">

     ✉

     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.

115. Line 2565, Column 15: required attribute "action" not specified

         <form name="#">

     ✉

     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>`.

116. Line 2566, Column 172: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

         …lue) location.href = selectedValue;">

     ✉

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

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

117. Line 2569, Column 71: cannot generate system identifier for general entity "cat1"

         …guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation 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.

118. Line 2569, Column 71: general entity "cat1" not defined and no default entity

         …guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation 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.

119. Line 2569, Column 75: reference not terminated by REFC delimiter

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

     ✉

     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.

120. Line 2569, Column 75: reference to external entity in attribute value

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

     ✉

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

121. Line 2569, Column 75: reference to entity "cat1" for which no system identifier could be generated

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

     ✉

     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.

122. Line 2569, Column 69: entity was defined here

         …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

123. Line 2569, Column 83: cannot generate system identifier for general entity "q"

         …/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     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.

124. Line 2569, Column 83: general entity "q" not defined and no default entity

         …/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     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.

125. Line 2569, Column 84: reference not terminated by REFC delimiter

         …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     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.

126. Line 2569, Column 84: reference to external entity in attribute value

         …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

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

127. Line 2569, Column 84: reference to entity "q" for which no system identifier could be generated

         …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     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.

128. Line 2569, Column 81: entity was defined here

         …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

129. Line 2569, Column 86: cannot generate system identifier for general entity "start"

         …dex_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     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.

130. Line 2569, Column 86: general entity "start" not defined and no default entity

         …dex_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     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.

131. Line 2569, Column 91: reference not terminated by REFC delimiter

         …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     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.

132. Line 2569, Column 91: reference to external entity in attribute value

         …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

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

133. Line 2569, Column 91: reference to entity "start" for which no system identifier could be generated

         …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     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.

134. Line 2569, Column 84: entity was defined here

         …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

135. Line 2570, Column 75: reference not terminated by REFC delimiter

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     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.

136. Line 2570, Column 75: reference to external entity in attribute value

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

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

137. Line 2570, Column 75: reference to entity "cat1" for which no system identifier could be generated

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     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.

138. Line 2569, Column 69: entity was defined here

         …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

139. Line 2570, Column 84: reference not terminated by REFC delimiter

         …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     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.

140. Line 2570, Column 84: reference to external entity in attribute value

         …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

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

141. Line 2570, Column 84: reference to entity "q" for which no system identifier could be generated

         …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     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.

142. Line 2569, Column 81: entity was defined here

         …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

143. Line 2570, Column 91: reference not terminated by REFC delimiter

         …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     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.

144. Line 2570, Column 91: reference to external entity in attribute value

         …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

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

145. Line 2570, Column 91: reference to entity "start" for which no system identifier could be generated

         …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     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.

146. Line 2569, Column 84: entity was defined here

         …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

147. Line 2571, Column 75: reference not terminated by REFC delimiter

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     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.

148. Line 2571, Column 75: reference to external entity in attribute value

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

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

149. Line 2571, Column 75: reference to entity "cat1" for which no system identifier could be generated

         …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     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.

150. Line 2569, Column 69: entity was defined here

         …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

151. Line 2571, Column 84: reference not terminated by REFC delimiter

         …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     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.

152. Line 2571, Column 84: reference to external entity in attribute value

         …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

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

153. Line 2571, Column 84: reference to entity "q" for which no system identifier could be generated

         …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     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.

154. Line 2569, Column 81: entity was defined here

         …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

155. Line 2571, Column 91: reference not terminated by REFC delimiter

         …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     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.

156. Line 2571, Column 91: reference to external entity in attribute value

         …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

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

157. Line 2571, Column 91: reference to entity "start" for which no system identifier could be generated

         …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     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.

158. Line 2569, Column 84: entity was defined here

         …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

159. Line 2786, Column 15: required attribute "action" not specified

         <form name="#">

     ✉

     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>`.

160. Line 2787, Column 13: ID "drp_filter" already defined

         <select id="drp_filter" name="drp_filter drp_nojs" onchange="var selectedValue =

     ✉

     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).

161. Line 2566, Column 12: ID "drp_filter" first defined here

         <select id="drp_filter" name="drp_filter drp_nojs" onchange="var selectedValue =

162. Line 2787, Column 231: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

         …h: 280px !important; color:#0076CC;">

     ✉

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

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

163. Line 2789, Column 3: "DOCTYPE" declaration not allowed in instance

         <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.or

     ✉

164. Line 2790, Column 43: document type does not allow element "html" here

         <html xmlns="http://www.w3.org/1999/xhtml">

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

165. Line 2796, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Albania  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

166. Line 2797, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Albania  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

167. Line 2798, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Algeria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

168. Line 2799, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Algeria  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

169. Line 2800, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Andorra  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

170. Line 2801, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Andorra  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

171. Line 2802, Column 65: document type does not allow element "option" here

         …="http://www.ar.terra.com/deportes/vancouver2010/" >Argentina - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

172. Line 2803, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Armenia  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

173. Line 2804, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Armenia  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

174. Line 2805, Column 42: document type does not allow element "option" here

         <option value="http://www.nos.nl/os2010" >Aruba - NOS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

175. Line 2806, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Aruba  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

176. Line 2807, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Aruba - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

177. Line 2808, Column 56: document type does not allow element "option" here

         <option value="http://www.foxtel.com.au/vancouver2010" >Australia - Foxtel</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

178. Line 2809, Column 49: document type does not allow element "option" here

         <option value="http://ninemsn.com.au/vancouver" >Australia - Nine</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

179. Line 2810, Column 48: document type does not allow element "option" here

         <option value="http://de.eurosport.yahoo.com " >Austria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

180. Line 2811, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Austria - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

181. Line 2812, Column 37: document type does not allow element "option" here

         <option value="http://sport.orf.at" >Austria - ORF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

182. Line 2813, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Azerbaijan  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

183. Line 2814, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Azerbaijan  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

184. Line 2815, Column 44: document type does not allow element "option" here

         <option value="http://olimpicgames.tvr.by" >Belarus -TVR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

185. Line 2816, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Belarus  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

186. Line 2817, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Belarus - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

187. Line 2818, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Belgium  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

188. Line 2819, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Belgium - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

189. Line 2820, Column 42: document type does not allow element "option" here

         <option value="http://www.rtbf.be/sport" >Belgium - RTBF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

190. Line 2821, Column 52: document type does not allow element "option" here

         <option value="http://www.sporza.be/vancouver2010" >Belgium - VRT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

191. Line 2822, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Bosnia and Herzegovina</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

192. Line 2823, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Bosnia and Herzegovina - Eurovision</opt

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

193. Line 2824, Column 60: document type does not allow element "option" here

         <option value="http://esportes.terra.com.br/vancouver2010" >Brazil - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

194. Line 2825, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >British Indian Ocean Territory</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

195. Line 2826, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >British Indian Ocean Territory  - Eurovi

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

196. Line 2827, Column 38: document type does not allow element "option" here

         <option value="http://winter.bnt.bg" >Bulgaria - BNT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

197. Line 2828, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Bulgaria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

198. Line 2829, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Bulgaria - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

199. Line 2830, Column 43: document type does not allow element "option" here

         <option value="http://www.ctvolympics.ca" >Canada - CTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

200. Line 2831, Column 45: document type does not allow element "option" here

         <option value="http://www.rdsolympiques.ca" >Canada - RDS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

201. Line 2832, Column 51: document type does not allow element "option" here

         <option value="http://www.rtve.es/vancouver-2010" >Canary Islands - RTVE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

202. Line 2833, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Canary Islands  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

203. Line 2834, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Canary Islands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

204. Line 2835, Column 65: document type does not allow element "option" here

         …="http://www.cl.terra.com/deportes/vancouver2010/" >Chile - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

205. Line 2836, Column 39: document type does not allow element "option" here

         <option value="http://sports.cntv.cn" >China, People's Republic of - CCTV</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

206. Line 2837, Column 57: document type does not allow element "option" here

         <option value="http://www.elta.tv/event/Vancouver2010/" >Chinese Taipei - ELTA</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

207. Line 2838, Column 65: document type does not allow element "option" here

         …="http://www.co.terra.com/deportes/vancouver2010/" >Colombia - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

208. Line 2839, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Costa Rica - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

209. Line 2840, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Croatia  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

210. Line 2841, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Croatia  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

211. Line 2842, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Cyprus  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

212. Line 2843, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Cyprus  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

213. Line 2844, Column 45: document type does not allow element "option" here

         <option value="http://www.ceskatelevize.cz" >Czech Republic - ceskatelevize</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

214. Line 2845, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Czech Republic  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

215. Line 2846, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Czech Republic - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

216. Line 2847, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Denmark  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

217. Line 2848, Column 42: document type does not allow element "option" here

         <option value="http://www.dr.dk/sporten" >Denmark - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

218. Line 2849, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Denmark - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

219. Line 2850, Column 42: document type does not allow element "option" here

         <option value="http://www.ol2010.tv2.dk" >Denmark - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

220. Line 2851, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Dominican Republic</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

221. Line 2852, Column 65: document type does not allow element "option" here

         …="http://www.ec.terra.com/deportes/vancouver2010/" >Ecuador - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

222. Line 2853, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Egypt  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

223. Line 2854, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Egypt  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

224. Line 2855, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >El Salvador - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

225. Line 2856, Column 39: document type does not allow element "option" here

         <option value="http://www.err.ee/om/" >Estonia - ERR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

226. Line 2857, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Estonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

227. Line 2858, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Estonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

228. Line 2859, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >Falkland Islands (Malvinas)  - Eurosport

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

229. Line 2860, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Falkland Islands (Malvinas) - Eurovision

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

230. Line 2861, Column 42: document type does not allow element "option" here

         <option value="http://www.dr.dk/sporten" >Faroe Islands - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

231. Line 2862, Column 42: document type does not allow element "option" here

         <option value="http://www.ol2010.tv2.dk" >Faroe Islands - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

232. Line 2863, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Faroe Islands - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

233. Line 2864, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Faroe Islands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

234. Line 2865, Column 31: document type does not allow element "option" here

         <option value="http://yle.fi" >Finland - YLE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

235. Line 2866, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Finland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

236. Line 2867, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Finland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

237. Line 2868, Column 54: document type does not allow element "option" here

         <option value="http://jo-vancouver-2010.francetv.fr" >France - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

238. Line 2869, Column 38: document type does not allow element "option" here

         <option value="http://eurosport.fr " >France - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

239. Line 2870, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >France - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

240. Line 2871, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >French Guyana - France Télévisions</opti

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

241. Line 2872, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >French Guyana - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

242. Line 2873, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >French Guyana - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

243. Line 2874, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >French Polynesia - France Télévisions</o

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

244. Line 2875, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >French Polynesia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

245. Line 2876, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >French Polynesia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

246. Line 2877, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >French Southern Territories  - France Té

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

247. Line 2878, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >French Southern Territories - Eurosport<

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

248. Line 2879, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >French Southern Territories - Eurovision

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

249. Line 2880, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Georgia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

250. Line 2881, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Georgia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

251. Line 2882, Column 48: document type does not allow element "option" here

         <option value="http://de.eurosport.yahoo.com " >Germany - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

252. Line 2883, Column 39: document type does not allow element "option" here

         <option value="http://olympia.ard.de" >Germany - ARD</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

253. Line 2884, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Germany - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

254. Line 2885, Column 39: document type does not allow element "option" here

         <option value="http://olympia.zdf.de" >Germany - ZDF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

255. Line 2886, Column 44: document type does not allow element "option" here

         <option value="http://www.bbc.co.uk/sport" >Gibraltar - BBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

256. Line 2887, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Gibraltar - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

257. Line 2888, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Gibraltar - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

258. Line 2889, Column 56: document type does not allow element "option" here

         <option value="http://news.ert.gr/sports/olympics2010" >Greece - ERT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

259. Line 2890, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Greece - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

260. Line 2891, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Greece - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

261. Line 2892, Column 42: document type does not allow element "option" here

         <option value="http://www.dr.dk/sporten" >Greenland - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

262. Line 2893, Column 42: document type does not allow element "option" here

         <option value="http://www.ol2010.tv2.dk" >Greenland - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

263. Line 2894, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Greenland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

264. Line 2895, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Greenland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

265. Line 2896, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >Guadeloupe - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

266. Line 2897, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Guadeloupe - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

267. Line 2898, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Guadeloupe - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

268. Line 2899, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Guatemala - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

269. Line 2900, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Honduras - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

270. Line 2901, Column 40: document type does not allow element "option" here

         <option value="http://www.i-cable.com" >Hong Kong - i-Cable</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

271. Line 2902, Column 43: document type does not allow element "option" here

         <option value="http://www.teliolimpia.hu" >Hungary - Magyar</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

272. Line 2903, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Hungary - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

273. Line 2904, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Hungary - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

274. Line 2905, Column 42: document type does not allow element "option" here

         <option value="http://www.ruv.is/ol2010" >Iceland - RUV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

275. Line 2906, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Iceland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

276. Line 2907, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Iceland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

277. Line 2908, Column 47: document type does not allow element "option" here

         <option value="http://uk.eurosport.yahoo.com" >Ireland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

278. Line 2909, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Ireland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

279. Line 2910, Column 45: document type does not allow element "option" here

         <option value="http://www.iba.org.il/sport" >Israel - IBA</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

280. Line 2911, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Israel - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

281. Line 2912, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Israel - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

282. Line 2913, Column 49: document type does not allow element "option" here

         <option value="http://www.vancouver2010.rai.it" >Italy - Rai</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

283. Line 2914, Column 45: document type does not allow element "option" here

         <option value="http://www.sky.it/olimpiadi" >Italy - Sky Italia</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

284. Line 2915, Column 37: document type does not allow element "option" here

         <option value="http://www.gorin.jp" >Japan - Gorin</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

285. Line 2916, Column 47: document type does not allow element "option" here

         <option value="http://www.nhk.or.jp/olympic " >Japan - NHK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

286. Line 2917, Column 44: document type does not allow element "option" here

         <option value="http://www.nhk-ondemand.jp" >Japan - NHK On Demand</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

287. Line 2918, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Jordan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

288. Line 2919, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Jordan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

289. Line 2920, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Kazakhstan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

290. Line 2921, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Kazakhstan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

291. Line 2922, Column 42: document type does not allow element "option" here

         <option value="http://olympic.sbs.co.kr" >Korea - SBS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

292. Line 2923, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Kyrgyzstan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

293. Line 2924, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Kyrgyzstan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

294. Line 2925, Column 36: document type does not allow element "option" here

         <option value="http://www.ltv7.lv" >Latvia - LTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

295. Line 2926, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Latvia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

296. Line 2927, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Latvia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

297. Line 2928, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Lebanon - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

298. Line 2929, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Lebanon - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

299. Line 2930, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Libya - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

300. Line 2931, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Libya - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

301. Line 2932, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Liechtenstein - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

302. Line 2933, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Liechtenstein - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

303. Line 2934, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Lithuania - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

304. Line 2935, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Lithuania - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

305. Line 2936, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Luxembourg - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

306. Line 2937, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Luxembourg - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

307. Line 2938, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Macedonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

308. Line 2939, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Macedonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

309. Line 2940, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Madeira - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

310. Line 2941, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Madeira - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

311. Line 2942, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Malta - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

312. Line 2943, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Malta - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

313. Line 2944, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >Martinique - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

314. Line 2945, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Martinique - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

315. Line 2946, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Martinique - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

316. Line 2947, Column 54: document type does not allow element "option" here

         <option value="http://jo-vancouver-2010.francetv.fr" >Mayotte - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

317. Line 2948, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Mayotte - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

318. Line 2949, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Mayotte - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

319. Line 2950, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Mexico - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

320. Line 2951, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >Moldova, Republic Of - Eurosport</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

321. Line 2952, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Moldova, Republic Of - Eurovision</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

322. Line 2953, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Monaco - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

323. Line 2954, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Monaco - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

324. Line 2955, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Montenegro - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

325. Line 2956, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Montenegro - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

326. Line 2957, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Morocco - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

327. Line 2958, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Morroco - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

328. Line 2959, Column 38: document type does not allow element "option" here

         <option value="http://nos.nl/os2010" >Netherlands - NOS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

329. Line 2960, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Netherlands - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

330. Line 2961, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Netherlands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

331. Line 2962, Column 42: document type does not allow element "option" here

         <option value="http://www.nos.nl/os2010" >Netherlands Antilles</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

332. Line 2963, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Netherlands Antilles</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

333. Line 2964, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Netherlands Antilles - Eurovision</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

334. Line 2965, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >New Caledonia - France Télévisions</opti

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

335. Line 2966, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >New Caledonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

336. Line 2967, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >New Caledonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

337. Line 2968, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Nicaragua - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

338. Line 2969, Column 38: document type does not allow element "option" here

         <option value="http://www.nrk.no/ol" >Norway - NRK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

339. Line 2970, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Norway - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

340. Line 2971, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Norway - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

341. Line 2972, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Panama - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

342. Line 2973, Column 65: document type does not allow element "option" here

         …="http://www.pe.terra.com/deportes/vancouver2010/" >Peru - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

343. Line 2974, Column 45: document type does not allow element "option" here

         <option value="http://vancouver2010.tvp.pl" >Poland - TVP</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

344. Line 2975, Column 37: document type does not allow element "option" here

         <option value="http://eurosport.pl" >Poland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

345. Line 2976, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Poland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

346. Line 2977, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Portugal - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

347. Line 2978, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Portugal - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

348. Line 2979, Column 54: document type does not allow element "option" here

         <option value="http://jo-vancouver-2010.francetv.fr" >Réunion - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

349. Line 2980, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Réunion - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

350. Line 2981, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Réunion - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

351. Line 2982, Column 43: document type does not allow element "option" here

         <option value="http://www.tvr.ro/Joiarna" >Romania - TVR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

352. Line 2983, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Romania - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

353. Line 2984, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Romania - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

354. Line 2985, Column 38: document type does not allow element "option" here

         <option value="http://eurosport.ru " >Russia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

355. Line 2986, Column 41: document type does not allow element "option" here

         <option value="http://www.1tv.ru/olimp" >Russia - C1R</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

356. Line 2987, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Russia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

357. Line 2988, Column 57: document type does not allow element "option" here

         <option value="http://video.sportbox.ru/olimpiada 2010" >Russia - RTR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

358. Line 2989, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >Saint Pierre And Miquelon - France Télév

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

359. Line 2990, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >Saint Pierre And Miquelon - Eurosport</o

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

360. Line 2991, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Saint Pierre And Miquelon - Eurovision</

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

361. Line 2992, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >San Marino - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

362. Line 2993, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >San Marino - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

363. Line 2994, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Serbia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

364. Line 2995, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Serbia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

365. Line 2996, Column 45: document type does not allow element "option" here

         <option value="http://www.stv.sk/vancouver" >Slovakia - STV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

366. Line 2997, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Slovakia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

367. Line 2998, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Slovakia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

368. Line 2999, Column 45: document type does not allow element "option" here

         <option value="http://www.rtvslo.si/oi2010" >Slovenia - RTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

369. Line 3000, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Slovenia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

370. Line 3001, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Slovenia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

371. Line 3002, Column 51: document type does not allow element "option" here

         <option value="http://www.rtve.es/vancouver-2010" >Spain - RTVE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

372. Line 3003, Column 48: document type does not allow element "option" here

         <option value="http://es.eurosport.yahoo.com " >Spain - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

373. Line 3004, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Spain - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

374. Line 3005, Column 41: document type does not allow element "option" here

         <option value="http://www.nrksport.net" >Spitsbergen - NRK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

375. Line 3006, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Spitsbergen - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

376. Line 3007, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Spitsbergen - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

377. Line 3008, Column 38: document type does not allow element "option" here

         <option value="http://www.svt.se/os" >Sweden - SVT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

378. Line 3009, Column 38: document type does not allow element "option" here

         <option value="http://eurosport.se " >Sweden - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

379. Line 3010, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Sweden - Eurovision </option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

380. Line 3011, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Switzerland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

381. Line 3012, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Switzerland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

382. Line 3013, Column 45: document type does not allow element "option" here

         <option value="http://www.rsi.ch/vancouver" >Switzerland - RSI</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

383. Line 3014, Column 44: document type does not allow element "option" here

         <option value="http://vancouver2010.sf.tv" >Switzerland - SF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

384. Line 3015, Column 54: document type does not allow element "option" here

         <option value="http://www.tsrsport.ch/vancouver2010" >Switzerland - TSR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

385. Line 3016, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Tajikistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

386. Line 3017, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Tajikistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

387. Line 3018, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >The Azores - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

388. Line 3019, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >The Azores - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

389. Line 3020, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Tunisia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

390. Line 3021, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Tunisia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

391. Line 3022, Column 39: document type does not allow element "option" here

         <option value="http://www.trt.net.tr" >Turkey - TRT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

392. Line 3023, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Turkey - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

393. Line 3024, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Turkey - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

394. Line 3025, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Turkmenistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

395. Line 3026, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Turkmenistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

396. Line 3027, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Ukraine - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

397. Line 3028, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Ukraine - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

398. Line 3029, Column 44: document type does not allow element "option" here

         <option value="http://www.bbc.co.uk/sport" >United Kingdom - BBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

399. Line 3030, Column 47: document type does not allow element "option" here

         <option value="http://uk.eurosport.yahoo.com" >United Kingdom - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

400. Line 3031, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >United Kingdom - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

401. Line 3032, Column 65: document type does not allow element "option" here

         …="http://www.mx.terra.com/deportes/vancouver2010/" >Uruguay - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

402. Line 3033, Column 44: document type does not allow element "option" here

         <option value="http://www.nbcolympics.com" >USA - NBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

403. Line 3034, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Uzbekistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

404. Line 3035, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Uzbekistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

405. Line 3036, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >Vatican City State (Holy See) - Eurospor

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

406. Line 3037, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Vatican City State (Holy See) - Eurovisi

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

407. Line 3038, Column 65: document type does not allow element "option" here

         …="http://www.ve.terra.com/deportes/vancouver2010/" >Venezuela - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

408. Line 3039, Column 44: document type does not allow element "option" here

         <option value="http://www.bbc.co.uk/sport" >Virgin Islands, British</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

409. Line 3040, Column 44: document type does not allow element "option" here

         … value="http://eurosport.yahoo.com" >Virgin Islands, British - Eurosport</opt

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

410. Line 3041, Column 57: document type does not allow element "option" here

         …//www.eurovisionsports.tv/olympics" >Virgin Islands, British - Eurovision</op

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

411. Line 3042, Column 54: document type does not allow element "option" here

         …tp://jo-vancouver-2010.francetv.fr" >Wallis And Futuna - France Télévisions</

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

412. Line 3043, Column 44: document type does not allow element "option" here

         <option value="http://eurosport.yahoo.com" >Wallis And Futuna - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

413. Line 3044, Column 57: document type does not allow element "option" here

         <option value="http://www.eurovisionsports.tv/olympics" >Wallis And Futuna - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

414. Line 3045, Column 9: end tag for "body" omitted, but OMITTAG NO was specified

         </select>

     ✉

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

415. Line 2795: start tag was here

         ><body>

416. Line 3045, Column 9: end tag for "html" omitted, but OMITTAG NO was specified

         </select>

     ✉

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

417. Line 2790: start tag was here

         ><html xmlns="http://www.w3.org/1999/xhtml">

418. Line 3146, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         …nternational Olympic Committee" rel=nofollow><img src="/gfx/00/17/22/ioc_18d-

     ✉

419. Line 3147, Column 107: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         …apore Youth Olympic Games 2010" rel=nofollow><img src="/gfx/00/13/35/singapor

     ✉

420. Line 3148, Column 81: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         …et="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-2

     ✉

421. Line 3149, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         …get="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-20

     ✉

422. Line 3150, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         …arget="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18/99/rio2016_

     ✉

423. Line 3220, Column 5: document type does not allow element "ul" here; assuming missing "li" start-tag

          <ul><br />

     ✉

424. Line 3220, Column 11: document type does not allow element "br" here; assuming missing "li" start-tag

          <ul><br />

     ✉

425. Line 3222, Column 5: document type does not allow element "li" here; missing one of "ul", "ol" start-tag

          <li><a href="/more-2010-information/olympic-torch-relay/olympic-torch-relay-int

     ✉

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

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

426. Line 3227, Column 5: document type does not allow element "li" here; missing one of "ul", "ol" start-tag

          <li><a href="/more-2010-information/olympic-torch-relay/about-the-olympic-torch

     ✉

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

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

427. Line 3228, Column 7: end tag for "li" omitted, but OMITTAG NO was specified

          </div>

     ✉

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

428. Line 3220, Column 5: start tag was here

          <ul><br />

429. Line 3228, Column 7: end tag for "ul" omitted, but OMITTAG NO was specified

          </div>

     ✉

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

430. Line 3220, Column 1: start tag was here

          <ul><br />

431. Line 3228, Column 7: end tag for "li" omitted, but OMITTAG NO was specified

          </div>

     ✉

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

432. Line 3220, Column 1: start tag was here

          <ul><br />

433. Line 3228, Column 7: end tag for "ul" omitted, but OMITTAG NO was specified

          </div>

     ✉

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

434. Line 3216, Column 1: start tag was here

          <ul>

435. Line 3259, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

         			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

436. Line 3298, Column 36: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

     ✉

     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.
437. Line 3298, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

          if (!(typeof nad === "undefined") && !nad)

     ✉

     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.
438. Line 169, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

         …d = document.location.protocol == "https:";    if (!nad) document.write(unesc…

     ✉

439. Line 169, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

         …d = document.location.protocol == "https:";    if (!nad) document.write(unesc…

     ✉

440. Line 244, Column 30: XML Parsing Error: AttValue: " or ' expected

         document.writeln('<style type=\"text/css\">');

     ✉

441. Line 244, Column 30: XML Parsing Error: attributes construct error

         document.writeln('<style type=\"text/css\">');

     ✉

442. Line 244, Column 30: XML Parsing Error: Couldn't find end of Start Tag style line 244

         document.writeln('<style type=\"text/css\">');

     ✉

443. Line 247, Column 26: XML Parsing Error: Opening and ending tag mismatch: script line 199 and style

         document.writeln('</style>');

     ✉

444. Line 248, Column 9: XML Parsing Error: Opening and ending tag mismatch: meta line 24 and script

         </script>

     ✉

445. Line 1012, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

         …/schedule---results/" title="Schedule & Results">Schedule & Results</a></li>…

     ✉

446. Line 1012, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

         …/schedule---results/" title="Schedule & Results">Schedule & Results</a></li>…

     ✉

447. Line 1123, Column 27: XML Parsing Error: AttValue: " or ' expected

         document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

448. Line 1123, Column 27: XML Parsing Error: attributes construct error

         document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

449. Line 1123, Column 27: XML Parsing Error: Couldn't find end of Start Tag div line 1123

         document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

450. Line 1123, Column 76: XML Parsing Error: AttValue: " or ' expected

         …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

451. Line 1123, Column 76: XML Parsing Error: attributes construct error

         …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

452. Line 1123, Column 76: XML Parsing Error: Couldn't find end of Start Tag div line 1123

         …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

453. Line 1139, Column 22: XML Parsing Error: Opening and ending tag mismatch: script line 1116 and div

         document.write("</div></div>");

     ✉

454. Line 1145, Column 9: XML Parsing Error: Opening and ending tag mismatch: div line 1059 and script

         </script>

     ✉

455. Line 1753, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …/accessories/let-the-games-begin/cataccessories-catopening-p1.html?utm_campai…

     ✉

456. Line 1753, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …/accessories/let-the-games-begin/cataccessories-catopening-p1.html?utm_campai…

     ✉

457. Line 1753, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …/accessories/let-the-games-begin/cataccessories-catopening-p1.html?utm_campai…

     ✉

458. Line 1778, Column 37: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

459. Line 1778, Column 38: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

460. Line 2200, Column 37: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

461. Line 2200, Column 38: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

462. Line 2532, Column 37: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

463. Line 2532, Column 38: XML Parsing Error: xmlParseEntityRef: no name

           if (!(typeof nad === "undefined") && !nad)

     ✉

464. Line 2569, Column 74: XML Parsing Error: EntityRef: expecting ';'

         …de/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Aler

     ✉

465. Line 2569, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</op…

     ✉

466. Line 2569, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</op…

     ✉

467. Line 2570, Column 74: XML Parsing Error: EntityRef: expecting ';'

         …de/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Aler

     ✉

468. Line 2570, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</op…

     ✉

469. Line 2570, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</op…

     ✉

470. Line 2571, Column 74: XML Parsing Error: EntityRef: expecting ';'

         …de/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</o

     ✉

471. Line 2571, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>…

     ✉

472. Line 2571, Column > 80: XML Parsing Error: EntityRef: expecting ';'

         …rts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>…

     ✉

473. Line 2789, Column 1: XML Parsing Error: StartTag: invalid element name

         <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.or

     ✉

474. Line 3045, Column 9: XML Parsing Error: Opening and ending tag mismatch: body line 2795 and select

         </select>

     ✉

475. Line 3046, Column 7: XML Parsing Error: Opening and ending tag mismatch: html line 2790 and form

         </form>

     ✉

476. Line 3047, Column 6: XML Parsing Error: Opening and ending tag mismatch: select line 2787 and div

         </div>

     ✉

477. Line 3048, Column > 80: XML Parsing Error: Opening and ending tag mismatch: form line 2786 and div

         …line" src="/gfx/00/23/57/broadcaster2_00d-ku.jpg" /></div>…

     ✉

478. Line 3146, Column > 80: XML Parsing Error: AttValue: " or ' expected

         …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

479. Line 3146, Column > 80: XML Parsing Error: attributes construct error

         …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

480. Line 3146, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3146

         …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

481. Line 3146, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3146 and a

         …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

482. Line 3146, Column > 80: XML Parsing Error: Opening and ending tag mismatch: ul line 3145 and li

         …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

483. Line 3147, Column > 80: XML Parsing Error: AttValue: " or ' expected

         …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

484. Line 3147, Column > 80: XML Parsing Error: attributes construct error

         …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

485. Line 3147, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3147

         …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

486. Line 3147, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3147 and a

         …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

487. Line 3147, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 3143 and li

         …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

488. Line 3148, Column > 80: XML Parsing Error: AttValue: " or ' expected

         …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

489. Line 3148, Column > 80: XML Parsing Error: attributes construct error

         …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

490. Line 3148, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3148

         …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

491. Line 3148, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3148 and a

         …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

492. Line 3148, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 3142 and li

         …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

493. Line 3149, Column 76: XML Parsing Error: AttValue: " or ' expected

         …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

494. Line 3149, Column 76: XML Parsing Error: attributes construct error

         …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

495. Line 3149, Column 76: XML Parsing Error: Couldn't find end of Start Tag a line 3149

         …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

496. Line 3149, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3149 and a

         …="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2014_…

     ✉

497. Line 3149, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 3125 and li

         …="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2014_…

     ✉

498. Line 3150, Column > 80: XML Parsing Error: AttValue: " or ' expected

         …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

499. Line 3150, Column > 80: XML Parsing Error: attributes construct error

         …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

500. Line 3150, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3150

         …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

501. Line 3150, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3150 and a

         …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

502. Line 3150, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 275 and li

         …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

503. Line 3151, Column 6: XML Parsing Error: Opening and ending tag mismatch: div line 274 and ul

          </ul>

     ✉

504. Line 3228, Column 7: XML Parsing Error: Opening and ending tag mismatch: ul line 3220 and div

          </div>

     ✉

505. Line 3247, Column 8: XML Parsing Error: Opening and ending tag mismatch: ul line 3216 and div

         		</div><!-- end of refLine -->

     ✉

506. Line 3259, Column 58: XML Parsing Error: AttValue: " or ' expected

         			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

507. Line 3259, Column 58: XML Parsing Error: attributes construct error

         			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

508. Line 3259, Column 58: XML Parsing Error: Couldn't find end of Start Tag a line 3259

         			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

509. Line 3259, Column 74: XML Parsing Error: Opening and ending tag mismatch: li line 3259 and a

         …ss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

510. Line 3259, Column > 80: XML Parsing Error: Opening and ending tag mismatch: ul line 3251 and li

         … title="RSS" rel=nofollow>RSS</a></li>…

     ✉

511. Line 3260, Column 5: XML Parsing Error: Opening and ending tag mismatch: div line 3250 and ul

         </ul>

     ✉

512. Line 3267, Column 7: XML Parsing Error: Opening and ending tag mismatch: body line 263 and div

          </div>

     ✉

513. Line 3286, Column 7: XML Parsing Error: Opening and ending tag mismatch: html line 2 and div

         	</div><!--end of wrapFooter-->

     ✉

514. Line 3297, Column 2: XML Parsing Error: Extra content at the end of the document

         		<script type="text/javascript">

     ✉

↑ Top