Quiniela, loto, quini 6, loto5, telekino, loteria, nacional, provincia, tombolas, quini6, brinco, quiniela poceada, monobingo, quiniela plus, resultado, sorteo, loterias, solidaria, prode, pozo de la quiniela, maradona, clubkeno, mibingo, totobingo, del azar de ...

tujugada.com.ar
  • Domain Name
    tujugada.com.ar
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #32412
  • Page Size
    247.2 KB
  • Ip Address
    173.192.19.70
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    136 GIF, 20 JPG, 2 PNG

Website Meta Analysis

  • Title
    quiniela quini 6 loto telekino resultado sorteo loteria brinco
  • Meta Keyword
    loto,quini,quini6,quini 6,telekino,loto5,quiniela,quinielas,sorteo,sorteos,resultado,resultados,prode,loterias,loterías,loteria,nacional,provincia,brinco,poceada,plus,pozo,mono,bingo,monobingo,solidaria,maradona,club,keno,clubkeno,mi,mibingo,toto,totobingo,extracto,tombola,hoy,ayer,casinos,bingos,poker,apuestas,billetes,comprar,ganar,jugar,ticket,azar,suerte,melate,polla,casinos,horoscopo,horóscopo,sueños,significado,noticias,rekino,tombolina
  • Meta Description
    Quiniela, loto, quini 6, loto5, telekino, loteria, nacional, provincia, tombolas, quini6, brinco, quiniela poceada, monobingo, quiniela plus, resultado, sorteo, loterias, solidaria, prode, pozo de la quiniela, maradona, clubkeno, mibingo, totobingo, del azar de Argentina y principales juegos de azar del mundo ...

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    173.192.19.70
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from tujugada.com.ar.

HTML Analysis

  • date: Tue, 07 Oct 2014 13:29:21 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • content-length: 215615
  • content-type: text/html
  • cache-control: private
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for tujugada.com.ar

IP 173.192.19.70 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 173.192.19.70

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 799 Errors
  • 26 Warnings
Ratio Text/Html
  • 0.6507291370430057
Message Error
  • Error Line 2, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Error Line 13, Column 32: required attribute "TYPE" not specified
      <script language="JavaScript">

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

  • Error Line 92, Column 7: end tag for element "HEAD" which is not open
    </head>

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

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

  • Error Line 94, Column 22: required attribute "TYPE" not specified
    <script src="home.js"></script>

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

  • Error Line 95, Column 30: required attribute "TYPE" not specified
    <script language="JavaScript">

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

  • Error Line 180, Column 30: required attribute "TYPE" not specified
    <script LANGUAGE="JavaScript">

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

  • Error Line 185, Column 44: end tag for element "TITLE" which is not open
    "<HEAD><TITLE>POLITICA DE PRIVACIDAD</TITLE></HEAD>");

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

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

  • Error Line 185, Column 51: end tag for element "HEAD" which is not open
    "<HEAD><TITLE>POLITICA DE PRIVACIDAD</TITLE></HEAD>");

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

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

  • Error Line 189, Column 31: end tag for element "B" which is not open
    "        <p ALIGN='CENTER'></b></u></font><BR> <b><font FACE='Verdana' SIZE='2'…

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

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

  • Error Line 189, Column 35: end tag for element "U" which is not open
    "        <p ALIGN='CENTER'></b></u></font><BR> <b><font FACE='Verdana' SIZE='2'…

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

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

  • Error Line 189, Column 42: end tag for element "FONT" which is not open
    …      <p ALIGN='CENTER'></b></u></font><BR> <b><font FACE='Verdana' SIZE='2'><…

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

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

  • Error Line 190, Column 5: end tag for element "P" which is not open
    "</p>" +

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

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

  • Error Line 191, Column 13: end tag for element "U" which is not open
    "        </u></font><font FACE='Verdana' SIZE='2'>" +

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

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

  • Error Line 191, Column 20: end tag for element "FONT" which is not open
    "        </u></font><font FACE='Verdana' SIZE='2'>" +

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

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

  • Error Line 193, Column 16: end tag for element "FONT" which is not open
    "        </font></b><font FACE='Verdana' SIZE='2'>" +

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

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

  • Error Line 193, Column 20: end tag for element "B" which is not open
    "        </font></b><font FACE='Verdana' SIZE='2'>" +

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

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

  • Error Line 194, Column 83: end tag for element "B" which is not open
    … <p ALIGN='JUSTIFY'><font face='Verdana' size='2'><BR><B>TuJugada.com.ar</B>" +

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

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

  • Error Line 201, Column 87: end tag for element "FONT" which is not open
    …ier modificaci&oacute;n sobre dichos datos cuando usted lo desee.</font></p>" +

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

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

  • Error Line 201, Column 91: end tag for element "P" which is not open
    …ier modificaci&oacute;n sobre dichos datos cuando usted lo desee.</font></p>" +

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

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

  • Error Line 211, Column 64: end tag for element "FONT" which is not open
    "        servicios y productos dentro de nuestro website.</font></p>" +

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

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

  • Error Line 211, Column 68: end tag for element "P" which is not open
    "        servicios y productos dentro de nuestro website.</font></p>" +

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

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

  • Error Line 224, Column 47: end tag for element "FONT" which is not open
    "        menos que se indique otra cosa.</font></p>" +

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

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

  • Error Line 224, Column 51: end tag for element "P" which is not open
    "        menos que se indique otra cosa.</font></p>" +

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

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

  • Error Line 237, Column 50: end tag for element "FONT" which is not open
    "        pueden no trabajar como se espera.</font></p>" +

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

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

  • Error Line 237, Column 54: end tag for element "P" which is not open
    "        pueden no trabajar como se espera.</font></p>" +

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

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

  • Error Line 240, Column 73: end tag for element "FONT" which is not open
    "        de comunicar cualquier modificaci&oacute;n en los mismos.</font></p>" +

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

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

  • Error Line 240, Column 77: end tag for element "P" which is not open
    "        de comunicar cualquier modificaci&oacute;n en los mismos.</font></p>" +

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

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

  • Error Line 243, Column 70: end tag for element "FONT" which is not open
    "        correspondiente consentimiento del usuario registrado.</font></p>" +

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

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

  • Error Line 243, Column 74: end tag for element "P" which is not open
    "        correspondiente consentimiento del usuario registrado.</font></p>" +

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

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

  • Error Line 249, Column 84: end tag for element "FONT" which is not open
    …tro de la Pol&iacute;tica de Confidencialidad de TuJugada.com.ar.</font></p>" +

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

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

  • Error Line 249, Column 88: end tag for element "P" which is not open
    …tro de la Pol&iacute;tica de Confidencialidad de TuJugada.com.ar.</font></p>" +

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

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

  • Error Line 257, Column 25: end tag for element "FONT" which is not open
    "        usuarios.</font></p>" +

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

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

  • Error Line 257, Column 29: end tag for element "P" which is not open
    "        usuarios.</font></p>" +

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

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

  • Error Line 258, Column 123: end tag for element "A" which is not open
    …'><img src='botoncerrar1.gif' border='0' width='66' height='19'></a><BR><BR>" +

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

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

  • Error Line 261, Column 10: end tag for element "CENTER" which is not open
    "</CENTER>" +

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

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

  • Error Line 262, Column 6: end tag for element "TD" which is not open
    "</td>" + 

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

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

  • Error Line 263, Column 6: end tag for element "TR" which is not open
    "</tr>" +

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

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

  • Error Line 264, Column 9: end tag for element "TABLE" which is not open
    "</table><BR>" +

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

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

  • Error Line 265, Column 10: end tag for element "CENTER" which is not open
    "</center>");

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

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

  • Error Line 269, Column 30: required attribute "TYPE" not specified
    <script language="JavaScript">

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

  • Error Line 276, Column 75: there is no attribute "HEIGHT"
        <table border="0" cellpadding="0" cellspacing="0" width="100%" height="80">

    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.

  • Error Line 282, Column 108: there is no attribute "LOWSRC"
    …der="0" src="logotujugada.gif" lowsrc="logotujugada_low.jpg" alt=" Resultados …

    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.

  • Error Line 285, Column 31: there is no attribute "BORDER"
                   <iframe border="0" width="600" height="70" src="Ini_Top_Top_468x…

    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.

  • Error Line 285, Column 103: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …ght="70" src="Ini_Top_Top_468x60.htm" frameborder="no" scrolling="no"></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 323, Column 36: required attribute "TYPE" not specified
    		    <script language="JavaScript">

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

  • Error Line 337, Column 233: document type does not allow element "A" here
    ….gif" alt="Registrate - Solo son unos pocos datos"><a><!-- Finish Copying -->		

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

  • Error Line 338, Column 14: end tag for "A" omitted, but its declaration does not permit this
            </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 337, Column 231: start tag was here
    ….gif" alt="Registrate - Solo son unos pocos datos"><a><!-- Finish Copying -->		
  • Error Line 338, Column 14: end tag for "A" omitted, but its declaration does not permit this
            </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 337, Column 29: start tag was here
      		  <!-- Start Copying --><a href="javascript:MM_openBrWindow('registracion1.…
  • Error Line 349, Column 98: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …"125" src="Ini_Izq_Top_125x125.htm" frameborder="no" scrolling="no"></iframe>		

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 395, Column 34: required attribute "TYPE" not specified
        <script language="JavaScript">

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

  • Error Line 644, Column 73: an attribute value must be a literal unless it contains only name characters
    …0 cellspacing=0 cellpadding=0 bgcolor=#FF9900 height=16>  <tr>   <td><p align=…

    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.

  • Error Line 644, Column 238: end tag for "B" omitted, but its declaration does not permit this
    …>RESULTADOS QUINIELAS ARGENTINAS</font></b></td>  </tr> </table> <table width=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 644, Column 198: start tag was here
    … sans-serif' size='1' color='#FFFFFF'><b>RESULTADOS QUINIELAS ARGENTINAS</font…
  • Error Line 644, Column 242: end tag for element "B" which is not open
    …ULTADOS QUINIELAS ARGENTINAS</font></b></td>  </tr> </table> <table width='100…

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

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

  • Error Line 644, Column 330: an attribute value must be a literal unless it contains only name characters
    …0 cellspacing=0 cellpadding=0 bgcolor=#FF9900>  <tr>   <td>    <table width=10…

    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.

  • Error Line 644, Column 371: an attribute value must be a literal unless it contains only name characters
    …9900>  <tr>   <td>    <table width=100% border=0 cellspacing=1 cellpadding=0> …

    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.

  • Error Line 644, Column 464: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 644, Column 522: there is no attribute "HEIGHT"
    …ng=0 cellpadding=3>        <tr height='30'> 	     <td bgcolor=#FFFFF0><p align…

    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.

  • Error Line 644, Column 546: an attribute value must be a literal unless it contains only name characters
    …   <tr height='30'> 	     <td bgcolor=#FFFFF0><p align='center'>            <d…

    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.

  • Error Line 644, Column 795: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 644, Column 877: an attribute value must be a literal unless it contains only name characters
    …   <tr height='30'> 	     <td bgcolor=#FFFFF0><p align='center'>            <d…

    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.

  • Error Line 644, Column 1143: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 644, Column 1226: an attribute value must be a literal unless it contains only name characters
    …  <tr height='151'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 644, Column 1631: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 644, Column 1363: start tag was here
    …tulo'>Quiniela <br>Nacional</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 644, Column 1711: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 644, Column 1794: an attribute value must be a literal unless it contains only name characters
    …  <tr height='151'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 644, Column 1882: ID "PREV_TITULO" already defined
    …_nacional.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 644, Column 2200: document type does not allow element "A" here
    …f='quiniela_nacional.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 644, Column 2211: ID "PREV_TITULO" already defined
    …_nacional.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 644, Column 2525: document type does not allow element "A" here
    …f='quiniela_nacional.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 644, Column 2536: ID "PREV_TITULO" already defined
    …_nacional.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 644, Column 2857: document type does not allow element "A" here
    …f='quiniela_nacional.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 644, Column 2868: ID "PREV_TITULO" already defined
    …_nacional.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 644, Column 3139: end tag for "A" omitted, but its declaration does not permit this
    …0'><b>El Cazador</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 644, Column 2813: start tag was here
    …b>La Zapatilla</b></font>			<br>		    <a href='quiniela_nacional.asp' class=mo…
  • Error Line 644, Column 3139: end tag for "A" omitted, but its declaration does not permit this
    …0'><b>El Cazador</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 644, Column 2481: start tag was here
    …00'><b>La mesa</b></font>			<br>		    <a href='quiniela_nacional.asp' class=mo…
  • Error Line 644, Column 3139: end tag for "A" omitted, but its declaration does not permit this
    …0'><b>El Cazador</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 644, Column 2156: start tag was here
    …b>Los Anteojos</b></font>			<br>		    <a href='quiniela_nacional.asp' class=mo…
  • Error Line 644, Column 3139: end tag for "A" omitted, but its declaration does not permit this
    …0'><b>El Cazador</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 644, Column 1827: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_nacional.asp' class=mo…
  • Error Line 644, Column 3285: an attribute value must be a literal unless it contains only name characters
    …0 cellspacing=0 cellpadding=0 bgcolor=#FF9900>  <tr>   <td>    <table width=10…

    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.

  • Error Line 644, Column 3326: an attribute value must be a literal unless it contains only name characters
    …9900>  <tr>   <td>    <table width=100% border=0 cellspacing=1 cellpadding=0> …

    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.

  • Error Line 645, Column 88: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …ght='60' src='Ini_Cab_Top_234x60.htm' frameborder='no' scrolling='no'></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 647, Column 55: end tag for "TABLE" omitted, but its declaration does not permit this
    …tr>        </table>	    </tr>	    </td>    <tr>      <td width='30%'>       <t…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 644, Column 3310: start tag was here
    …ng=0 bgcolor=#FF9900>  <tr>   <td>    <table width=100% border=0 cellspacing=1…
  • Error Line 647, Column 109: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 192: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 298: ID "PREV_TITULO" already defined
    …aires.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Buenos<br>Aires…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 375: ID "PREV_TEXTO_PRECIO" already defined
    …s</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 648: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 349: start tag was here
    …Quiniela<br>Buenos<br>Aires</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 647, Column 728: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 811: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 913: ID "PREV_TITULO" already defined
    …nos_aires.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 997: ID "PREV_TEXTO_PRECIO" already defined
    …bsp;	       <font class=prc><span id='prev_texto_precio'></span></font><font f…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 1302: document type does not allow element "A" here
    …ovincia_buenos_aires.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 647, Column 1313: ID "PREV_TITULO" already defined
    …nos_aires.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 1398: ID "PREV_TEXTO_PRECIO" already defined
    …bsp;	       <font class=prc><span id='prev_texto_precio'></span></font><font f…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 1702: document type does not allow element "A" here
    …ovincia_buenos_aires.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 647, Column 1713: ID "PREV_TITULO" already defined
    …nos_aires.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 1800: ID "PREV_TEXTO_PRECIO" already defined
    …bsp;	       <font class=prc><span id='prev_texto_precio'></span></font><font f…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 2107: document type does not allow element "A" here
    …ovincia_buenos_aires.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 647, Column 2118: ID "PREV_TITULO" already defined
    …nos_aires.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 2203: ID "PREV_TEXTO_PRECIO" already defined
    …bsp;	       <font class=prc><span id='prev_texto_precio'></span></font><font f…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 2447: end tag for "A" omitted, but its declaration does not permit this
    …00'><b>La Sangre</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 2049: start tag was here
    …b>La Desgracia</b></font>			<br>		    <a href='quiniela_provincia_buenos_aires…
  • Error Line 647, Column 2447: end tag for "A" omitted, but its declaration does not permit this
    …00'><b>La Sangre</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 1644: start tag was here
    …'><b>La Virgen</b></font>			<br>		    <a href='quiniela_provincia_buenos_aires…
  • Error Line 647, Column 2447: end tag for "A" omitted, but its declaration does not permit this
    …00'><b>La Sangre</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 1244: start tag was here
    …><b>El Ahogado</b></font>			<br>		    <a href='quiniela_provincia_buenos_aires…
  • Error Line 647, Column 2447: end tag for "A" omitted, but its declaration does not permit this
    …00'><b>La Sangre</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 844: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_provincia_buenos_aires…
  • Error Line 647, Column 2545: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 2627: an attribute value must be a literal unless it contains only name characters
    …   <tr height='70'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 2718: ID "PREV_TITULO" already defined
    …uguay.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Uruguay</span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 2787: ID "PREV_TEXTO_PRECIO" already defined
    …y</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 3011: end tag for "FONT" omitted, but its declaration does not permit this
    … Uruguaya' border='0'></a> 	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 2761: start tag was here
    …titulo'>Quiniela<br>Uruguay</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 647, Column 3091: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 3173: an attribute value must be a literal unless it contains only name characters
    …   <tr height='70'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 3260: ID "PREV_TITULO" already defined
    …a_uruguay.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 3345: ID "PREV_TEXTO_PRECIO" already defined
    …bsp;	       <font class=prc><span id='prev_texto_precio'></span></font><font f…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 3635: document type does not allow element "A" here
    …ef='quiniela_uruguay.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 647, Column 3646: ID "PREV_TITULO" already defined
    …a_uruguay.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 3731: ID "PREV_TEXTO_PRECIO" already defined
    …bsp;	       <font class=prc><span id='prev_texto_precio'></span></font><font f…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 3972: end tag for "A" omitted, but its declaration does not permit this
    …8000'><b>La mesa</b></font>	      </td> 	    </tr> 	   </table>      </td>    …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 3592: start tag was here
    …<b>La Escopeta</b></font>			<br>		    <a href='quiniela_uruguay.asp' class=mod…
  • Error Line 647, Column 3972: end tag for "A" omitted, but its declaration does not permit this
    …8000'><b>La mesa</b></font>	      </td> 	    </tr> 	   </table>      </td>    …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 3206: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_uruguay.asp' class=mod…
  • Error Line 647, Column 4072: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 4155: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 4247: ID "PREV_TITULO" already defined
    …ta_fe.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Santa Fé</span>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 4317: ID "PREV_TEXTO_PRECIO" already defined
    …é</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 4597: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 4291: start tag was here
    …itulo'>Quiniela<br>Santa Fé</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 647, Column 4677: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 4760: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 4848: ID "PREV_TITULO" already defined
    …_santa_fe.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 5162: document type does not allow element "A" here
    …f='quiniela_santa_fe.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 647, Column 5173: ID "PREV_TITULO" already defined
    …_santa_fe.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 5487: document type does not allow element "A" here
    …f='quiniela_santa_fe.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 647, Column 5498: ID "PREV_TITULO" already defined
    …_santa_fe.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 5565: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 647, Column 5822: document type does not allow element "A" here
    …f='quiniela_santa_fe.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 647, Column 5833: ID "PREV_TITULO" already defined
    …_santa_fe.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 6104: end tag for "A" omitted, but its declaration does not permit this
    …0'><b>La Manteca</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 5778: start tag was here
    …0'><b>La carne</b></font>			<br>		    <a href='quiniela_santa_fe.asp' class=mo…
  • Error Line 647, Column 6104: end tag for "A" omitted, but its declaration does not permit this
    …0'><b>La Manteca</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 5443: start tag was here
    …00'><b>La rata</b></font>			<br>		    <a href='quiniela_santa_fe.asp' class=mo…
  • Error Line 647, Column 6104: end tag for "A" omitted, but its declaration does not permit this
    …0'><b>La Manteca</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 5118: start tag was here
    …0'><b>El barco</b></font>			<br>		    <a href='quiniela_santa_fe.asp' class=mo…
  • Error Line 647, Column 6104: end tag for "A" omitted, but its declaration does not permit this
    …0'><b>La Manteca</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 4793: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_santa_fe.asp' class=mo…
  • Error Line 647, Column 6202: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 6285: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 6376: ID "PREV_TITULO" already defined
    …rdoba.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Córdoba</span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 6445: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 6723: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 6419: start tag was here
    …titulo'>Quiniela<br>Córdoba</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 647, Column 6803: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 6886: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 6973: ID "PREV_TITULO" already defined
    …a_cordoba.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 7286: document type does not allow element "A" here
    …ef='quiniela_cordoba.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 647, Column 7297: ID "PREV_TITULO" already defined
    …a_cordoba.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 7614: document type does not allow element "A" here
    …ef='quiniela_cordoba.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 647, Column 7625: ID "PREV_TITULO" already defined
    …a_cordoba.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 7692: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 647, Column 7951: document type does not allow element "A" here
    …ef='quiniela_cordoba.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 647, Column 7962: ID "PREV_TITULO" already defined
    …a_cordoba.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 8234: end tag for "A" omitted, but its declaration does not permit this
    …'><b>El Cuchillo</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 7908: start tag was here
    …<b>El Jorobado</b></font>			<br>		    <a href='quiniela_cordoba.asp' class=mod…
  • Error Line 647, Column 8234: end tag for "A" omitted, but its declaration does not permit this
    …'><b>El Cuchillo</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 7571: start tag was here
    …<b>El Dentista</b></font>			<br>		    <a href='quiniela_cordoba.asp' class=mod…
  • Error Line 647, Column 8234: end tag for "A" omitted, but its declaration does not permit this
    …'><b>El Cuchillo</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 7243: start tag was here
    …0'><b>El cerro</b></font>			<br>		    <a href='quiniela_cordoba.asp' class=mod…
  • Error Line 647, Column 8234: end tag for "A" omitted, but its declaration does not permit this
    …'><b>El Cuchillo</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 6919: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_cordoba.asp' class=mod…
  • Error Line 647, Column 8332: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 8415: an attribute value must be a literal unless it contains only name characters
    …  <tr height='100'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 8518: ID "PREV_TITULO" already defined
    …stero.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Santiago<br>del…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 8605: ID "PREV_TEXTO_PRECIO" already defined
    …o</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 8850: end tag for "FONT" omitted, but its declaration does not permit this
    …el Estero' border='0'></a> 	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 8579: start tag was here
    …r>Santiago<br>del<br>Estero</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 647, Column 8930: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 9013: an attribute value must be a literal unless it contains only name characters
    …  <tr height='100'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 9112: ID "PREV_TITULO" already defined
    …el_estero.asp' class=modtit><span id='prev_titulo'>Matutina- 28/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 9439: document type does not allow element "A" here
    …_santiago_del_estero.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 647, Column 9450: ID "PREV_TITULO" already defined
    …el_estero.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 9517: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 647, Column 9787: document type does not allow element "A" here
    …_santiago_del_estero.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 647, Column 9798: ID "PREV_TITULO" already defined
    …el_estero.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 10070: end tag for "A" omitted, but its declaration does not permit this
    …'><b>La Linterna</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 9732: start tag was here
    …><b>La Iglesia</b></font>			<br>		    <a href='quiniela_santiago_del_estero.as…
  • Error Line 647, Column 10070: end tag for "A" omitted, but its declaration does not permit this
    …'><b>La Linterna</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 9384: start tag was here
    …'><b>El Balcon</b></font>			<br>		    <a href='quiniela_santiago_del_estero.as…
  • Error Line 647, Column 10070: end tag for "A" omitted, but its declaration does not permit this
    …'><b>La Linterna</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 9046: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_santiago_del_estero.as…
  • Error Line 647, Column 10168: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 10251: an attribute value must be a literal unless it contains only name characters
    …  <tr height='112'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 10342: ID "PREV_TITULO" already defined
    …ndoza.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Mendoza</span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 10411: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 647, Column 10689: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 10385: start tag was here
    …titulo'>Quiniela<br>Mendoza</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 647, Column 10769: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 647, Column 10852: an attribute value must be a literal unless it contains only name characters
    …  <tr height='112'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 647, Column 10939: ID "PREV_TITULO" already defined
    …a_mendoza.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 11257: document type does not allow element "A" here
    …ef='quiniela_mendoza.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 647, Column 11268: ID "PREV_TITULO" already defined
    …a_mendoza.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 11335: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 647, Column 11593: document type does not allow element "A" here
    …ef='quiniela_mendoza.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 647, Column 11604: ID "PREV_TITULO" already defined
    …a_mendoza.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 647, Column 11872: end tag for "A" omitted, but its declaration does not permit this
    …8000'><b>El Papa</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 11550: start tag was here
    …><b>Los Negros</b></font>			<br>		    <a href='quiniela_mendoza.asp' class=mod…
  • Error Line 647, Column 11872: end tag for "A" omitted, but its declaration does not permit this
    …8000'><b>El Papa</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 11214: start tag was here
    …b>Los Ladrones</b></font>			<br>		    <a href='quiniela_mendoza.asp' class=mod…
  • Error Line 647, Column 11872: end tag for "A" omitted, but its declaration does not permit this
    …8000'><b>El Papa</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 647, Column 10885: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_mendoza.asp' class=mod…
  • Error Line 648, Column 19: end tag for "DIV" omitted, but its declaration does not permit this
                  </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 635, Column 9: start tag was here
            <div align="center">
  • Error Line 654, Column 110: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …0" src="Ini_Top_Der_Medio_234x60.htm" frameborder="no" scrolling="no"></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 656, Column 141: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …250_R3.htm" id="frame1" name="frame1" frameborder="no" scrolling="no"></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 658, Column 46: required attribute "TYPE" not specified
                    <script language="JavaScript">

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

  • Error Line 1000, Column 82: an attribute value must be a literal unless it contains only name characters
    …0 cellspacing=0 cellpadding=0 bgcolor=#B51D2F height=16>  <tr>   <td><p align=…

    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.

  • Error Line 1000, Column 321: an attribute value must be a literal unless it contains only name characters
    …0 cellspacing=0 cellpadding=0 bgcolor=#B51D2F>  <tr>   <td>     <table width=1…

    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.

  • Error Line 1000, Column 363: an attribute value must be a literal unless it contains only name characters
    …D2F>  <tr>   <td>     <table width=100% border=0 cellspacing=1 cellpadding=0> …

    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.

  • Error Line 1000, Column 456: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 538: an attribute value must be a literal unless it contains only name characters
    …   <tr height='30'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 790: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 872: an attribute value must be a literal unless it contains only name characters
    …   <tr height='30'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 1122: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 1204: an attribute value must be a literal unless it contains only name characters
    …   <tr height='30'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 1474: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 1556: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'> 		    <a href…

    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.

  • Error Line 1000, Column 1639: ID "PREV_TITULO" already defined
    …o_new.asp' class=modtit> 			<span id='prev_titulo'>Loto</span></a><font class=…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 1693: ID "PREV_TEXTO_PRECIO" already defined
    …o</span></a><font class=prc><span id='prev_texto_precio'></span><a href='loto_…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 1865: end tag for "FONT" omitted, but its declaration does not permit this
    … del Loto' border='0'></a> 	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 1667: start tag was here
    …<span id='prev_titulo'>Loto</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 1946: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 2028: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 2266: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 2348: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 2612: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 2694: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'> 		    <a href…

    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.

  • Error Line 1000, Column 2778: ID "PREV_TITULO" already defined
    …5_new.asp' class=modtit> 			<span id='prev_titulo'>Loto5</span></a><font class…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 2833: ID "PREV_TEXTO_PRECIO" already defined
    …5</span></a><font class=prc><span id='prev_texto_precio'></span><a href='loto5…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 3008: end tag for "FONT" omitted, but its declaration does not permit this
    …del Loto5' border='0'></a> 	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 2807: start tag was here
    …span id='prev_titulo'>Loto5</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 3089: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 3171: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 3409: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 3491: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 3752: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 3834: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'> 		    <a href…

    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.

  • Error Line 1000, Column 3919: ID "PREV_TITULO" already defined
    …6_new.asp' class=modtit> 			<span id='prev_titulo'>Quini6</span></a><font clas…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 3975: ID "PREV_TEXTO_PRECIO" already defined
    …6</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 4152: end tag for "FONT" omitted, but its declaration does not permit this
    …l Quini 6' border='0'></a> 	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 3949: start tag was here
    …pan id='prev_titulo'>Quini6</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 4233: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 4315: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 4553: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 4635: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 4899: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 4981: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'> 		    <a hre…

    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.

  • Error Line 1000, Column 5067: ID "PREV_TITULO" already defined
    …o_new.asp' class=modtit> 			<span id='prev_titulo'>Brinco</span></a><font clas…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 5123: ID "PREV_TEXTO_PRECIO" already defined
    …o</span></a><font class=prc><span id='prev_texto_precio'></span><a href='brinc…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 5299: end tag for "FONT" omitted, but its declaration does not permit this
    …el Brinco' border='0'></a> 	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 5097: start tag was here
    …pan id='prev_titulo'>Brinco</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 5380: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 5462: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'>            <…

    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.

  • Error Line 1000, Column 5701: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 5783: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'>            <…

    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.

  • Error Line 1000, Column 6045: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 6127: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'> 		    <a href…

    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.

  • Error Line 1000, Column 6215: ID "PREV_TITULO" already defined
    …o_new.asp' class=modtit> 			<span id='prev_titulo'>Mono Bingo</span></a><font …

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 6275: ID "PREV_TEXTO_PRECIO" already defined
    …o</span></a><font class=prc><span id='prev_texto_precio'></span><a href='monob…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 6453: end tag for "A" omitted, but its declaration does not permit this
    …del Mono Bingo' border='0'>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 6301: start tag was here
    …c><span id='prev_texto_precio'></span><a href='monobingo_new.asp'>&nbsp;<img s…
  • Error Line 1000, Column 6453: end tag for "FONT" omitted, but its declaration does not permit this
    …del Mono Bingo' border='0'>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 6249: start tag was here
    …id='prev_titulo'>Mono Bingo</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 6533: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 6615: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 6851: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 6933: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 7188: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 7270: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'> 		    <a href…

    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.

  • Error Line 1000, Column 7354: ID "PREV_TITULO" already defined
    …e_new.asp' class=modtit> 			<span id='prev_titulo'>Prode</span></a><font class…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 7409: ID "PREV_TEXTO_PRECIO" already defined
    …e</span></a><font class=prc><span id='prev_texto_precio'></span><a href='prode…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 7578: end tag for "A" omitted, but its declaration does not permit this
    …rteo del Prode' border='0'>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 7435: start tag was here
    …c><span id='prev_texto_precio'></span><a href='prode_new.asp'>&nbsp;<img src='…
  • Error Line 1000, Column 7578: end tag for "FONT" omitted, but its declaration does not permit this
    …rteo del Prode' border='0'>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 7383: start tag was here
    …span id='prev_titulo'>Prode</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 7658: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 7740: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 7976: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 8058: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 8316: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 8398: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'> 		    <a hre…

    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.

  • Error Line 1000, Column 8486: ID "PREV_TITULO" already defined
    …o_new.asp' class=modtit> 			<span id='prev_titulo'>Telekino</span></a><font cl…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 8544: ID "PREV_TEXTO_PRECIO" already defined
    …o</span></a><font class=prc><span id='prev_texto_precio'></span><a href='telek…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 8723: end tag for "FONT" omitted, but its declaration does not permit this
    …l telekino' border='0'></a>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 8518: start tag was here
    …n id='prev_titulo'>Telekino</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 8804: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 8886: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'>            <…

    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.

  • Error Line 1000, Column 9125: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 9207: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'>            <…

    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.

  • Error Line 1000, Column 9469: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 9551: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'> 		    <a href…

    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.

  • Error Line 1000, Column 9637: ID "PREV_TITULO" already defined
    …a_new.asp' class=modtit> 			<span id='prev_titulo'>Poceada</span></a><font cla…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 9694: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='pocea…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 9882: end tag for "FONT" omitted, but its declaration does not permit this
    …la poceada' border='0'></a>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 9668: start tag was here
    …an id='prev_titulo'>Poceada</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 9963: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 10045: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 10284: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 10366: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 10627: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 10709: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'> 		    <a href…

    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.

  • Error Line 1000, Column 10792: ID "PREV_TITULO" already defined
    …s_new.asp' class=modtit> 			<span id='prev_titulo'>Quiniela Plus</span></a><fo…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 10855: ID "PREV_TEXTO_PRECIO" already defined
    …s</span></a><font class=prc><span id='prev_texto_precio'></span><a href='plus_…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 11037: end tag for "FONT" omitted, but its declaration does not permit this
    …niela plus' border='0'></a>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 10829: start tag was here
    …'prev_titulo'>Quiniela Plus</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 11118: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 11200: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 11439: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 11521: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 11782: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 11864: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'> 		    <a href…

    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.

  • Error Line 1000, Column 11947: ID "PREV_TITULO" already defined
    …abola.asp' class=modtit> 			<span id='prev_titulo'>MegaBola</span></a><font cl…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 12005: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='megab…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 12188: end tag for "FONT" omitted, but its declaration does not permit this
    … Mega Bola' border='0'></a>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 11979: start tag was here
    …n id='prev_titulo'>MegaBola</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 12269: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 12351: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 12589: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 12671: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 12934: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 13016: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'> 		    <a hre…

    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.

  • Error Line 1000, Column 13105: ID "PREV_TITULO" already defined
    …a_new.asp' class=modtit> 			<span id='prev_titulo'>La Solidaria</span></a><fon…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 13167: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='solid…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 13358: end tag for "FONT" omitted, but its declaration does not permit this
    … solidaria' border='0'></a>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 13141: start tag was here
    …='prev_titulo'>La Solidaria</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 13439: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 13521: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'>            <…

    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.

  • Error Line 1000, Column 13761: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 13843: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'>            <…

    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.

  • Error Line 1000, Column 14102: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 14184: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'> 		    <a href…

    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.

  • Error Line 1000, Column 14271: ID "PREV_TITULO" already defined
    …o_new.asp' class=modtit> 			<span id='prev_titulo'>Club Keno</span></a><font c…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 14330: ID "PREV_TEXTO_PRECIO" already defined
    …o</span></a><font class=prc><span id='prev_texto_precio'></span><a href='clubk…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 14521: end tag for "FONT" omitted, but its declaration does not permit this
    …Bonaerense' border='0'></a>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 14304: start tag was here
    … id='prev_titulo'>Club Keno</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 14602: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 14684: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 14923: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 15005: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 15261: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 15343: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'> 		    <a href…

    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.

  • Error Line 1000, Column 15430: ID "PREV_TITULO" already defined
    …a_new.asp' class=modtit> 			<span id='prev_titulo'>J C/Maradona</span></a><fon…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 15492: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='marad…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 15678: end tag for "FONT" omitted, but its declaration does not permit this
    … Maradona' border='0'></a> 	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 15466: start tag was here
    …='prev_titulo'>J C/Maradona</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 15759: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 15841: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 16077: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 16159: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0><p align='center'>            <d…

    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.

  • Error Line 1000, Column 16419: an attribute value must be a literal unless it contains only name characters
    …td width='39%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 16501: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'> 		    <a hre…

    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.

  • Error Line 1000, Column 16585: ID "PREV_TITULO" already defined
    …o_new.asp' class=modtit> 			<span id='prev_titulo'>Pozo Quiniela</span></a><fo…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1000, Column 16648: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='pozo_…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1000, Column 16834: end tag for "FONT" omitted, but its declaration does not permit this
    …a Quiniela' border='0'></a>	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 16622: start tag was here
    …'prev_titulo'>Pozo Quiniela</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1000, Column 16915: an attribute value must be a literal unless it contains only name characters
    …td width='25%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 16997: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'>            <…

    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.

  • Error Line 1000, Column 17237: an attribute value must be a literal unless it contains only name characters
    …td width='35%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1000, Column 17319: an attribute value must be a literal unless it contains only name characters
    …   <tr height='20'> 	     <td bgcolor=#F0F0F0 ><p align='center'>            <…

    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.

  • Error Line 1000, Column 17532: end tag for "TABLE" omitted, but its declaration does not permit this
    …  </table> 	  </td>      </tr>    </tr>   </table> 	    </td>   </tr> </table>…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1000, Column 347: start tag was here
    …g=0 bgcolor=#B51D2F>  <tr>   <td>     <table width=100% border=0 cellspacing=1…
  • Error Line 1003, Column 19: end tag for element "TD" which is not open
                  </td>

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

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

  • Error Line 1004, Column 56: document type does not allow element "TD" here
                 <td valign="top" align="center" width="2%">

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

  • Error Line 1009, Column 18: end tag for element "TR" which is not open
                 </tr>

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

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

  • Error Line 1010, Column 20: end tag for element "TABLE" which is not open
                </table>

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

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

  • Error Line 1011, Column 16: end tag for "CENTER" omitted, but its declaration does not permit this
              </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 316, Column 3: start tag was here
      <center>
  • Error Line 1012, Column 13: end tag for element "TD" which is not open
            </td>

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

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

  • Error Line 1013, Column 70: document type does not allow element "TD" here
            <td width="18%" valign="top" align="center" bgcolor="#EBEADE">

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

  • Error Line 1028, Column 46: required attribute "TYPE" not specified
                    <script language="JavaScript">

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

  • Error Line 1041, Column 23: an attribute value must be a literal unless it contains only name characters
              <TD bgColor=#800040 height=20><FONT class=btntit>&nbsp;AZAR ITALIA</F…

    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.

  • Error Line 1127, Column 23: an attribute value must be a literal unless it contains only name characters
              <TD bgColor=#800040 height=20><FONT class=btntit>&nbsp;AZAR ALEMANIA<…

    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.

  • Error Line 1185, Column 11: end tag for element "TR" which is not open
          </tr>

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

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

  • Error Line 1186, Column 11: end tag for element "TABLE" which is not open
       </table>

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

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

  • Error Line 1187, Column 11: end tag for element "CENTER" which is not open
      </center>

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

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

  • Error Line 1188, Column 6: end tag for element "DIV" which is not open
    </div>

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

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

  • Error Line 1196, Column 32: required attribute "TYPE" not specified
    		<script language="JavaScript">

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

  • Error Line 1241, Column 37: an attribute value must be a literal unless it contains only name characters
              <TD height=20 onclick=mClk(this); 

    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.

  • Error Line 1253, Column 37: an attribute value must be a literal unless it contains only name characters
              <TD height=20 onclick=mClk(this); 

    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.

  • Error Line 1265, Column 37: an attribute value must be a literal unless it contains only name characters
              <TD height=20 onclick=mClk(this); 

    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.

  • Error Line 1276, Column 37: an attribute value must be a literal unless it contains only name characters
              <TD height=20 onclick=mClk(this); 

    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.

  • Error Line 1349, Column 23: an attribute value must be a literal unless it contains only name characters
              <TD bgColor=#800040 height=20><FONT class=btntit>&nbsp;AZAR CHILE</FO…

    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.

  • Warning Line 1417, Column 182: unclosed start-tag requires SHORTTAG YES
    …Loterias Gana Diario de Perú: Resultados de los sorteos Gana Diario - Perú"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 1426, Column 167: unclosed start-tag requires SHORTTAG YES
    …f" alt="Loterias GanaGol de Perú: Resultados de los sorteos GanaGol - Perú"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 1435, Column 171: unclosed start-tag requires SHORTTAG YES
    …lt="Loterias La Kabala de Perú: Resultados de los sorteos La Kabala - Perú"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 1444, Column 146: unclosed start-tag requires SHORTTAG YES
    …r="0" src="new1.gif" alt="Super3: Resultados de los sorteos Super 3 - Perú"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 1453, Column 167: unclosed start-tag requires SHORTTAG YES
    … alt="Loterias La Tinka de Perú: Resultados de los sorteos La Tinka - Perú"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 1462, Column 179: unclosed start-tag requires SHORTTAG YES
    …Loterias El reventon de Perú: Resultados de los sorteos el reventon - Perú"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Error Line 1578, Column 23: an attribute value must be a literal unless it contains only name characters
              <TD bgColor=#800040 height=20><FONT class=btntit>&nbsp;AZAR CANADA</F…

    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.

  • Error Line 1694, Column 23: an attribute value must be a literal unless it contains only name characters
              <TD bgColor=#800040 height=20><FONT class=btntit>&nbsp;AZAR FRANCIA</…

    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.

  • Error Line 1806, Column 23: an attribute value must be a literal unless it contains only name characters
              <TD bgColor=#800040 height=20><FONT class=btntit>&nbsp;AZAR BRASIL</F…

    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.

  • Error Line 1931, Column 73: an attribute value must be a literal unless it contains only name characters
    …0 cellspacing=0 cellpadding=0 bgcolor=#FF9900>  <tr>   <td>    <table width=10…

    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.

  • Error Line 1931, Column 114: an attribute value must be a literal unless it contains only name characters
    …9900>  <tr>   <td>    <table width=100% border=0 cellspacing=1 cellpadding=0> …

    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.

  • Error Line 1932, Column 100: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …'250' src='Ini_Cab_Medio_300x250.htm' frameborder='no' scrolling='no'></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1934, Column 47: end tag for "TABLE" omitted, but its declaration does not permit this
    …td>		</tr>     </table>	  </tr>	  </td>    <tr>      <td width='30%'>       <t…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1931, Column 98: start tag was here
    …ng=0 bgcolor=#FF9900>  <tr>   <td>    <table width=100% border=0 cellspacing=1…
  • Error Line 1934, Column 101: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1934, Column 184: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1934, Column 278: ID "PREV_TITULO" already defined
    …_rios.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Entre Ríos</spa…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 350: ID "PREV_TEXTO_PRECIO" already defined
    …s</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1934, Column 711: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 324: start tag was here
    …ulo'>Quiniela<br>Entre Ríos</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1934, Column 791: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1934, Column 874: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1934, Column 964: ID "PREV_TITULO" already defined
    …ntre_rios.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 1283: document type does not allow element "A" here
    …'quiniela_entre_rios.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 1934, Column 1294: ID "PREV_TITULO" already defined
    …ntre_rios.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 1612: document type does not allow element "A" here
    …'quiniela_entre_rios.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 1934, Column 1623: ID "PREV_TITULO" already defined
    …ntre_rios.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 1690: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 1934, Column 1952: document type does not allow element "A" here
    …'quiniela_entre_rios.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1934, Column 1963: ID "PREV_TITULO" already defined
    …ntre_rios.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 2235: end tag for "A" omitted, but its declaration does not permit this
    …'><b>El Jorobado</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 1906: start tag was here
    …<b>El Cocinero</b></font>			<br>		    <a href='quiniela_entre_rios.asp' class=…
  • Error Line 1934, Column 2235: end tag for "A" omitted, but its declaration does not permit this
    …'><b>El Jorobado</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 1566: start tag was here
    …'><b>El Aceite</b></font>			<br>		    <a href='quiniela_entre_rios.asp' class=…
  • Error Line 1934, Column 2235: end tag for "A" omitted, but its declaration does not permit this
    …'><b>El Jorobado</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 1237: start tag was here
    …<b>El Serrucho</b></font>			<br>		    <a href='quiniela_entre_rios.asp' class=…
  • Error Line 1934, Column 2235: end tag for "A" omitted, but its declaration does not permit this
    …'><b>El Jorobado</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 907: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_entre_rios.asp' class=…
  • Error Line 1934, Column 2333: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1934, Column 2416: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1934, Column 2507: ID "PREV_TITULO" already defined
    …cuman.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Tucumán</span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 2576: ID "PREV_TEXTO_PRECIO" already defined
    …n</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1934, Column 2928: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 2550: start tag was here
    …titulo'>Quiniela<br>Tucumán</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1934, Column 3008: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1934, Column 3091: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1934, Column 3178: ID "PREV_TITULO" already defined
    …a_tucuman.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 3502: document type does not allow element "A" here
    …ef='quiniela_tucuman.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 1934, Column 3513: ID "PREV_TITULO" already defined
    …a_tucuman.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 3830: document type does not allow element "A" here
    …ef='quiniela_tucuman.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 1934, Column 3841: ID "PREV_TITULO" already defined
    …a_tucuman.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 3908: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 1934, Column 4165: document type does not allow element "A" here
    …ef='quiniela_tucuman.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1934, Column 4176: ID "PREV_TITULO" already defined
    …a_tucuman.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 4450: end tag for "A" omitted, but its declaration does not permit this
    …<b>La Inundacion</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 4122: start tag was here
    …'><b>El Muerto</b></font>			<br>		    <a href='quiniela_tucuman.asp' class=mod…
  • Error Line 1934, Column 4450: end tag for "A" omitted, but its declaration does not permit this
    …<b>La Inundacion</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 3787: start tag was here
    …<b>Los Tomates</b></font>			<br>		    <a href='quiniela_tucuman.asp' class=mod…
  • Error Line 1934, Column 4450: end tag for "A" omitted, but its declaration does not permit this
    …<b>La Inundacion</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 3459: start tag was here
    …erto que habla</b></font>			<br>		    <a href='quiniela_tucuman.asp' class=mod…
  • Error Line 1934, Column 4450: end tag for "A" omitted, but its declaration does not permit this
    …<b>La Inundacion</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 3124: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_tucuman.asp' class=mod…
  • Error Line 1934, Column 4548: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1934, Column 4631: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1934, Column 4723: ID "PREV_TITULO" already defined
    …iones.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Misiones</span>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 4793: ID "PREV_TEXTO_PRECIO" already defined
    …s</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1934, Column 5148: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 4767: start tag was here
    …itulo'>Quiniela<br>Misiones</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1934, Column 5228: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1934, Column 5311: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1934, Column 5399: ID "PREV_TITULO" already defined
    …_misiones.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 5718: document type does not allow element "A" here
    …f='quiniela_misiones.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 1934, Column 5729: ID "PREV_TITULO" already defined
    …_misiones.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 6048: document type does not allow element "A" here
    …f='quiniela_misiones.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 1934, Column 6059: ID "PREV_TITULO" already defined
    …_misiones.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 6126: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 1934, Column 6387: document type does not allow element "A" here
    …f='quiniela_misiones.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1934, Column 6398: ID "PREV_TITULO" already defined
    …_misiones.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 6672: end tag for "A" omitted, but its declaration does not permit this
    …<b>La Inundacion</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 6343: start tag was here
    …b>La Desgracia</b></font>			<br>		    <a href='quiniela_misiones.asp' class=mo…
  • Error Line 1934, Column 6672: end tag for "A" omitted, but its declaration does not permit this
    …<b>La Inundacion</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 6004: start tag was here
    …b>Los Ladrones</b></font>			<br>		    <a href='quiniela_misiones.asp' class=mo…
  • Error Line 1934, Column 6672: end tag for "A" omitted, but its declaration does not permit this
    …<b>La Inundacion</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 5674: start tag was here
    …>El Mal tiempo</b></font>			<br>		    <a href='quiniela_misiones.asp' class=mo…
  • Error Line 1934, Column 6672: end tag for "A" omitted, but its declaration does not permit this
    …<b>La Inundacion</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 5344: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_misiones.asp' class=mo…
  • Error Line 1934, Column 6770: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1934, Column 6853: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1934, Column 6947: ID "PREV_TITULO" already defined
    …entes.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Corrientes</spa…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 7019: ID "PREV_TEXTO_PRECIO" already defined
    …s</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1934, Column 7380: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 6993: start tag was here
    …ulo'>Quiniela<br>Corrientes</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1934, Column 7460: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1934, Column 7543: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1934, Column 7633: ID "PREV_TITULO" already defined
    …orrientes.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 7952: document type does not allow element "A" here
    …'quiniela_corrientes.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 1934, Column 7963: ID "PREV_TITULO" already defined
    …orrientes.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 8280: document type does not allow element "A" here
    …'quiniela_corrientes.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 1934, Column 8291: ID "PREV_TITULO" already defined
    …orrientes.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 8358: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 1934, Column 8620: document type does not allow element "A" here
    …'quiniela_corrientes.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1934, Column 8631: ID "PREV_TITULO" already defined
    …orrientes.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 8911: end tag for "A" omitted, but its declaration does not permit this
    …rto sue&ntilde;o</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 8574: start tag was here
    …<b>El Excusado</b></font>			<br>		    <a href='quiniela_corrientes.asp' class=…
  • Error Line 1934, Column 8911: end tag for "A" omitted, but its declaration does not permit this
    …rto sue&ntilde;o</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 8234: start tag was here
    …0'><b>La bocha</b></font>			<br>		    <a href='quiniela_corrientes.asp' class=…
  • Error Line 1934, Column 8911: end tag for "A" omitted, but its declaration does not permit this
    …rto sue&ntilde;o</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 7906: start tag was here
    …<b>El Incendio</b></font>			<br>		    <a href='quiniela_corrientes.asp' class=…
  • Error Line 1934, Column 8911: end tag for "A" omitted, but its declaration does not permit this
    …rto sue&ntilde;o</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 7576: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_corrientes.asp' class=…
  • Error Line 1934, Column 9009: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1934, Column 9092: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1934, Column 9183: ID "PREV_TITULO" already defined
    …uquen.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Neuquen</span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 9252: ID "PREV_TEXTO_PRECIO" already defined
    …n</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1934, Column 9604: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 9226: start tag was here
    …titulo'>Quiniela<br>Neuquen</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1934, Column 9684: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1934, Column 9767: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1934, Column 9854: ID "PREV_TITULO" already defined
    …a_neuquen.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 10165: document type does not allow element "A" here
    …ef='quiniela_neuquen.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 1934, Column 10176: ID "PREV_TITULO" already defined
    …a_neuquen.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 10495: document type does not allow element "A" here
    …ef='quiniela_neuquen.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 1934, Column 10506: ID "PREV_TITULO" already defined
    …a_neuquen.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 10573: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 1934, Column 10830: document type does not allow element "A" here
    …ef='quiniela_neuquen.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1934, Column 10841: ID "PREV_TITULO" already defined
    …a_neuquen.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1934, Column 11110: end tag for "A" omitted, but its declaration does not permit this
    …000'><b>El miedo</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 10787: start tag was here
    …'><b>El Anillo</b></font>			<br>		    <a href='quiniela_neuquen.asp' class=mod…
  • Error Line 1934, Column 11110: end tag for "A" omitted, but its declaration does not permit this
    …000'><b>El miedo</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 10452: start tag was here
    …>El Cementerio</b></font>			<br>		    <a href='quiniela_neuquen.asp' class=mod…
  • Error Line 1934, Column 11110: end tag for "A" omitted, but its declaration does not permit this
    …000'><b>El miedo</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 10122: start tag was here
    …000'><b>El pan</b></font>			<br>		    <a href='quiniela_neuquen.asp' class=mod…
  • Error Line 1934, Column 11110: end tag for "A" omitted, but its declaration does not permit this
    …000'><b>El miedo</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1934, Column 9800: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_neuquen.asp' class=mod…
  • Error Line 1935, Column 98: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …t='60' src='Ini_Cab_Medio_234x60.htm' frameborder='no' scrolling='no'></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1937, Column 47: end tag for "TABLE" omitted, but its declaration does not permit this
    …td>		</tr>     </table>	  </tr>	  </td>    <tr>      <td width='30%'>       <t…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1931, Column 8: start tag was here
     			   <table width='100%' border=0 cellspacing=0 cellpadding=0 bgcolor=#FF9900…
  • Error Line 1937, Column 101: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 184: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 275: ID "PREV_TITULO" already defined
    …rmosa.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Formosa</span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 344: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1937, Column 696: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 318: start tag was here
    …titulo'>Quiniela<br>Formosa</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1937, Column 776: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 859: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 946: ID "PREV_TITULO" already defined
    …a_Formosa.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 1259: document type does not allow element "A" here
    …ef='quiniela_Formosa.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 1937, Column 1270: ID "PREV_TITULO" already defined
    …a_Formosa.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 1583: document type does not allow element "A" here
    …ef='quiniela_Formosa.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 1937, Column 1594: ID "PREV_TITULO" already defined
    …a_Formosa.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 1661: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 1937, Column 1919: document type does not allow element "A" here
    …ef='quiniela_Formosa.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1937, Column 1930: ID "PREV_TITULO" already defined
    …a_Formosa.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 2199: end tag for "A" omitted, but its declaration does not permit this
    …000'><b>La carne</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 1876: start tag was here
    …><b>El Soldado</b></font>			<br>		    <a href='quiniela_Formosa.asp' class=mod…
  • Error Line 1937, Column 2199: end tag for "A" omitted, but its declaration does not permit this
    …000'><b>La carne</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 1540: start tag was here
    …00'><b>El loco</b></font>			<br>		    <a href='quiniela_Formosa.asp' class=mod…
  • Error Line 1937, Column 2199: end tag for "A" omitted, but its declaration does not permit this
    …000'><b>La carne</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 1216: start tag was here
    …0'><b>El peine</b></font>			<br>		    <a href='quiniela_Formosa.asp' class=mod…
  • Error Line 1937, Column 2199: end tag for "A" omitted, but its declaration does not permit this
    …000'><b>La carne</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 892: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_Formosa.asp' class=mod…
  • Error Line 1937, Column 2297: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 2380: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 2469: ID "PREV_TITULO" already defined
    …Chaco.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Chaco</span></a…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 2536: ID "PREV_TEXTO_PRECIO" already defined
    …o</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1937, Column 2882: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 2510: start tag was here
    …v_titulo'>Quiniela<br>Chaco</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1937, Column 2962: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 3045: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 3130: ID "PREV_TITULO" already defined
    …ela_Chaco.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 3444: document type does not allow element "A" here
    …href='quiniela_Chaco.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 1937, Column 3455: ID "PREV_TITULO" already defined
    …ela_Chaco.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 3767: document type does not allow element "A" here
    …href='quiniela_Chaco.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2…

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

  • Error Line 1937, Column 3778: ID "PREV_TITULO" already defined
    …ela_Chaco.asp' class=modtit><span id='prev_titulo'>Vespertina- 27/2/2013</span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 3845: end tag for element "FONT" which is not open
    …/2013</span>&nbsp;&nbsp;	       </font><font face='Verdana, Arial, Helvetica, …

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

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

  • Error Line 1937, Column 4098: document type does not allow element "A" here
    …href='quiniela_Chaco.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1937, Column 4109: ID "PREV_TITULO" already defined
    …ela_Chaco.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 4379: end tag for "A" omitted, but its declaration does not permit this
    …00'><b>El Muerto</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 4057: start tag was here
    …00'><b>El Humo</b></font>			<br>		    <a href='quiniela_Chaco.asp' class=modti…
  • Error Line 1937, Column 4379: end tag for "A" omitted, but its declaration does not permit this
    …00'><b>El Muerto</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 3726: start tag was here
    …0'><b>La leche</b></font>			<br>		    <a href='quiniela_Chaco.asp' class=modti…
  • Error Line 1937, Column 4379: end tag for "A" omitted, but its declaration does not permit this
    …00'><b>El Muerto</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 3403: start tag was here
    …<b>La Sorpresa</b></font>			<br>		    <a href='quiniela_Chaco.asp' class=modti…
  • Error Line 1937, Column 4379: end tag for "A" omitted, but its declaration does not permit this
    …00'><b>El Muerto</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 3078: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_Chaco.asp' class=modti…
  • Error Line 1937, Column 4477: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 4560: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 4649: ID "PREV_TITULO" already defined
    …Salta.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>Salta</span></a…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 4716: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1937, Column 5062: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 4690: start tag was here
    …v_titulo'>Quiniela<br>Salta</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1937, Column 5142: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 5225: an attribute value must be a literal unless it contains only name characters
    …  <tr height='130'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 5310: ID "PREV_TITULO" already defined
    …ela_Salta.asp' class=modtit><span id='prev_titulo'>Primera- 28/2/2013</span>&n…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 5622: document type does not allow element "A" here
    …href='quiniela_Salta.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2…

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

  • Error Line 1937, Column 5633: ID "PREV_TITULO" already defined
    …ela_Salta.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 5948: document type does not allow element "A" here
    …href='quiniela_Salta.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1937, Column 5959: ID "PREV_TITULO" already defined
    …ela_Salta.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 6231: end tag for "A" omitted, but its declaration does not permit this
    …'><b>La Sorpresa</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 5907: start tag was here
    …<b>El Dentista</b></font>			<br>		    <a href='quiniela_Salta.asp' class=modti…
  • Error Line 1937, Column 6231: end tag for "A" omitted, but its declaration does not permit this
    …'><b>La Sorpresa</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 5581: start tag was here
    …'><b>La Sangre</b></font>			<br>		    <a href='quiniela_Salta.asp' class=modti…
  • Error Line 1937, Column 6231: end tag for "A" omitted, but its declaration does not permit this
    …'><b>La Sorpresa</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 5258: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_Salta.asp' class=modti…
  • Error Line 1937, Column 6329: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 6412: an attribute value must be a literal unless it contains only name characters
    …  <tr height='100'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 6504: ID "PREV_TITULO" already defined
    …_luis.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>San Luis</span>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 6574: ID "PREV_TEXTO_PRECIO" already defined
    …s</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1937, Column 6929: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 6548: start tag was here
    …itulo'>Quiniela<br>San Luis</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1937, Column 7009: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 7092: an attribute value must be a literal unless it contains only name characters
    …  <tr height='100'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 7180: ID "PREV_TITULO" already defined
    …_san_luis.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 7495: document type does not allow element "A" here
    …f='quiniela_san_luis.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1937, Column 7506: ID "PREV_TITULO" already defined
    …_san_luis.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 7775: end tag for "A" omitted, but its declaration does not permit this
    …000'><b>La Caida</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 7451: start tag was here
    …0'><b>La carne</b></font>			<br>		    <a href='quiniela_san_luis.asp' class=mo…
  • Error Line 1937, Column 7775: end tag for "A" omitted, but its declaration does not permit this
    …000'><b>La Caida</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 7125: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_san_luis.asp' class=mo…
  • Error Line 1937, Column 7873: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 7956: an attribute value must be a literal unless it contains only name characters
    …  <tr height='100'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 8048: ID "PREV_TITULO" already defined
    …rioja.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>La Rioja</span>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 8118: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1937, Column 8473: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 8092: start tag was here
    …itulo'>Quiniela<br>La Rioja</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1937, Column 8553: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 8636: an attribute value must be a literal unless it contains only name characters
    …  <tr height='100'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 8724: ID "PREV_TITULO" already defined
    …_La_rioja.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 9040: document type does not allow element "A" here
    …f='quiniela_La_rioja.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1937, Column 9051: ID "PREV_TITULO" already defined
    …_La_rioja.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 9320: end tag for "A" omitted, but its declaration does not permit this
    …00'><b>El Medico</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 8996: start tag was here
    …><b>El Caballo</b></font>			<br>		    <a href='quiniela_La_rioja.asp' class=mo…
  • Error Line 1937, Column 9320: end tag for "A" omitted, but its declaration does not permit this
    …00'><b>El Medico</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 8669: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_La_rioja.asp' class=mo…
  • Error Line 1937, Column 9418: an attribute value must be a literal unless it contains only name characters
    …td width='30%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 9501: an attribute value must be a literal unless it contains only name characters
    …  <tr height='100'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 9593: ID "PREV_TITULO" already defined
    …_juan.asp' class=modtit> 			<span id='prev_titulo'>Quiniela<br>San Juan</span>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 9663: ID "PREV_TEXTO_PRECIO" already defined
    …n</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 1937, Column 10018: end tag for "FONT" omitted, but its declaration does not permit this
    …r>&nbsp;	        <br>&nbsp;	      </td> 	    </tr> 	   </table> 	  </td>      …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 9637: start tag was here
    …itulo'>Quiniela<br>San Juan</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 1937, Column 10098: an attribute value must be a literal unless it contains only name characters
    …td width='70%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 1937, Column 10181: an attribute value must be a literal unless it contains only name characters
    …  <tr height='100'> 	     <td bgcolor=#FFFFF0><p align='center'> 		    <a href…

    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.

  • Error Line 1937, Column 10269: ID "PREV_TITULO" already defined
    …_san_juan.asp' class=modtit><span id='prev_titulo'>Matutina- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 10585: document type does not allow element "A" here
    …f='quiniela_san_juan.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2…

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

  • Error Line 1937, Column 10596: ID "PREV_TITULO" already defined
    …_san_juan.asp' class=modtit><span id='prev_titulo'>Nocturna- 27/2/2013</span>&…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1937, Column 10871: end tag for "A" omitted, but its declaration does not permit this
    …b>La nina Bonita</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 10541: start tag was here
    …'><b>La Ramera</b></font>			<br>		    <a href='quiniela_san_juan.asp' class=mo…
  • Error Line 1937, Column 10871: end tag for "A" omitted, but its declaration does not permit this
    …b>La nina Bonita</b></font>	      </td> 	    </tr> 	   </table> 	  </td>     <…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1937, Column 10214: start tag was here
    …olor=#FFFFF0><p align='center'> 		    <a href='quiniela_san_juan.asp' class=mo…
  • Error Line 1937, Column 10934: end tag for "DIV" omitted, but its declaration does not permit this
    …	    </tr> 	   </table> 	  </td>     </tr>    </table>   </td>  </tr> </table> 
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1923, Column 9: start tag was here
            <div align="center">
  • Error Line 1939, Column 124: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …b_Abajo_300x250_R0.htm" id="frame130" frameborder="no" scrolling="no"></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1941, Column 45: literal is missing closing delimiter
    …          <table width="100%" border=" border="3" cellspacing="3"" bordercolor…

    Did you forget to close a (double) quote mark?

  • Error Line 1941, Column 55: character data is not allowed here
    …<table width="100%" border=" border="3" cellspacing="3"" bordercolor="#CC3300"…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 1945, Column 125: end tag for "U" omitted, but its declaration does not permit this
    …>Encuentra aquí los resultados actualizados de los sorteos de Colombia:</b></u>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1945, Column 49: start tag was here
    …Face="Tahoma, Sans-serif" size="2"><b><u>Encuentra aquí los resultados actuali…
  • Error Line 1945, Column 129: end tag for element "U" which is not open
    …>Encuentra aquí los resultados actualizados de los sorteos de Colombia:</b></u>

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

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

  • Error Line 1947, Column 54: ID "PREV_TITULO" already defined
    …a href="Baloto.asp" class="modtit"><span id='prev_titulo'>Baloto</span></a> |		

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1948, Column 61: ID "PREV_TITULO" already defined
    …_Mañana.asp" class="modtit"><span id='prev_titulo'>El Dorado Mañana</span></a>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1949, Column 60: ID "PREV_TITULO" already defined
    …o_Tarde.asp" class="modtit"><span id='prev_titulo'>El Dorado Tarde</span></a> …

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1950, Column 60: ID "PREV_TITULO" already defined
    …o_Noche.asp" class="modtit"><span id='prev_titulo'>El Dorado Noche</span></a> …

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1951, Column 55: ID "PREV_TITULO" already defined
    …ref="Cachaco.asp" class="modtit"><span id='prev_titulo'>El Cachaco</span></a> |

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1952, Column 54: ID "PREV_TITULO" already defined
    … href="Culona.asp" class="modtit"><span id='prev_titulo'>La Culona</span></a> |

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1953, Column 57: ID "PREV_TITULO" already defined
    …ef="Astro_Sol.asp" class="modtit"><span id='prev_titulo'>Astro Sol</span></a> |

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1954, Column 58: ID "PREV_TITULO" already defined
    …="Astro_Luna.asp" class="modtit"><span id='prev_titulo'>Astro Luna</span></a> |

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1955, Column 62: ID "PREV_TITULO" already defined
    …hree_Dia.asp" class="modtit"><span id='prev_titulo'>Cash Three Día</span></a> |

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1956, Column 64: ID "PREV_TITULO" already defined
    …e_Noche.asp" class="modtit"><span id='prev_titulo'>Cash Three Noche</span></a>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1957, Column 61: ID "PREV_TITULO" already defined
    …_Four_Dia.asp" class="modtit"><span id='prev_titulo'>Play Four Día</span></a> |

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1958, Column 63: ID "PREV_TITULO" already defined
    …r_Noche.asp" class="modtit"><span id='prev_titulo'>Play Four Noche</span></a> …

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1959, Column 60: ID "PREV_TITULO" already defined
    …jao_de_Oro.asp" class="modtit"><span id='prev_titulo'>Pijao de Oro</span></a> |

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1960, Column 57: ID "PREV_TITULO" already defined
    …ef="Cuyabrito.asp" class="modtit"><span id='prev_titulo'>Cuyabrito</span></a> |

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1961, Column 59: ID "PREV_TITULO" already defined
    …Paisita_Dia.asp" class="modtit"><span id='prev_titulo'>Paisita Día</span></a> |

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1962, Column 61: ID "PREV_TITULO" already defined
    …a_Noche.asp" class="modtit"><span id='prev_titulo'>Paisita Noche</span></a> |	…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1963, Column 71: ID "PREV_TITULO" already defined
    …namarca.asp" class="modtit"><span id='prev_titulo'>Lotería de Cundinamarca</sp…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1964, Column 63: ID "PREV_TITULO" already defined
    …_Tolima.asp" class="modtit"><span id='prev_titulo'>Lotería del Tolima</span></…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1965, Column 71: ID "PREV_TITULO" already defined
    …uz_Roja.asp" class="modtit"><span id='prev_titulo'>Lotería de la Cruz Roja</sp…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1966, Column 65: ID "PREV_TITULO" already defined
    …l_Huila.asp" class="modtit"><span id='prev_titulo'>Lotería del Huila</span></a…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1967, Column 64: ID "PREV_TITULO" already defined
    …el_Meta.asp" class="modtit"><span id='prev_titulo'>Lotería del Meta</span></a>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1968, Column 65: ID "PREV_TITULO" already defined
    …l_Valle.asp" class="modtit"><span id='prev_titulo'>Lotería del Valle</span></a…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1969, Column 68: ID "PREV_TITULO" already defined
    …nizales.asp" class="modtit"><span id='prev_titulo'>Lotería de Manizales</span>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1970, Column 65: ID "PREV_TITULO" already defined
    …_Bogota.asp" class="modtit"><span id='prev_titulo'>Lotería de Bogotá</span></a…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1971, Column 67: ID "PREV_TITULO" already defined
    …Quindio.asp" class="modtit"><span id='prev_titulo'>Lotería del Quindío</span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1972, Column 68: ID "PREV_TITULO" already defined
    …ntander.asp" class="modtit"><span id='prev_titulo'>Lotería de Santander</span>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1973, Column 67: ID "PREV_TITULO" already defined
    …edellin.asp" class="modtit"><span id='prev_titulo'>Lotería de Medellín</span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1974, Column 68: ID "PREV_TITULO" already defined
    …saralda.asp" class="modtit"><span id='prev_titulo'>Lotería de Risaralda</span>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1975, Column 65: ID "PREV_TITULO" already defined
    …_Boyaca.asp" class="modtit"><span id='prev_titulo'>Lotería de Boyacá</span></a…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1976, Column 65: ID "PREV_TITULO" already defined
    …l_Cauca.asp" class="modtit"><span id='prev_titulo'>Lotería del Cauca</span></a…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 1984, Column 18: end tag for element "TD" which is not open
                 </td>

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

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

  • Error Line 1985, Column 56: document type does not allow element "TD" here
                 <td valign="top" align="center" width="2%">

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

  • Error Line 1989, Column 57: document type does not allow element "TD" here
                 <td valign="top" align="center" width="40%">

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

  • Error Line 1992, Column 72: there is no attribute "BORDERCOLOR"
    …ORDER-COLLAPSE: collapse" borderColor="#ff6600" cellSpacing="0" cellPadding="0…

    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.

  • Error Line 2016, Column 453: an attribute value must be a literal unless it contains only name characters
    …td width='40%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 535: an attribute value must be a literal unless it contains only name characters
    …   <tr height='25'> 	     <td bgcolor=#F0F0F><p align='center'>            <b>…

    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.

  • Error Line 2016, Column 743: an attribute value must be a literal unless it contains only name characters
    …<td width='60%'>      <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 823: an attribute value must be a literal unless it contains only name characters
    …    <tr height='25'> 	    <td bgcolor=#F0F0F0><p align='center'>          <b><…

    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.

  • Error Line 2016, Column 1047: an attribute value must be a literal unless it contains only name characters
    …td width='40%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 1129: an attribute value must be a literal unless it contains only name characters
    …   <tr height='25'> 	     <td bgcolor=#F0F0F0><p align='left'>		    <a href='l…

    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.

  • Error Line 2016, Column 1217: ID "PREV_TITULO" already defined
    …sticas.asp' class=modtit>			<span id='prev_titulo'>Loto</span></a><font class=…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2016, Column 1271: ID "PREV_TEXTO_PRECIO" already defined
    …o</span></a><font class=prc><span id='prev_texto_precio'></span><a href='loto_…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2016, Column 1444: end tag for "FONT" omitted, but its declaration does not permit this
    …del Loto' border='0'></a>         </td>	    </tr>	   </table>	  </td>      <td…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2016, Column 1245: start tag was here
    …<span id='prev_titulo'>Loto</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 2016, Column 1519: an attribute value must be a literal unless it contains only name characters
    …<td width='60%'>      <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 1857: an attribute value must be a literal unless it contains only name characters
    …td width='40%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 1939: an attribute value must be a literal unless it contains only name characters
    …   <tr height='25'> 	     <td bgcolor=#F0F0F0><p align='left'>		    <a href='q…

    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.

  • Error Line 2016, Column 2029: ID "PREV_TITULO" already defined
    …sticas.asp' class=modtit>			<span id='prev_titulo'>Quini6</span></a><font clas…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2016, Column 2085: ID "PREV_TEXTO_PRECIO" already defined
    …6</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2016, Column 2262: end tag for "FONT" omitted, but its declaration does not permit this
    …l Quini6' border='0'></a>         </td>	    </tr>	   </table>	  </td>      <td…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2016, Column 2059: start tag was here
    …pan id='prev_titulo'>Quini6</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 2016, Column 2337: an attribute value must be a literal unless it contains only name characters
    …<td width='60%'>      <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 2676: an attribute value must be a literal unless it contains only name characters
    …td width='40%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 2758: an attribute value must be a literal unless it contains only name characters
    …   <tr height='25'> 	     <td bgcolor=#F0F0F0><p align='left'>		    <a href='b…

    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.

  • Error Line 2016, Column 2848: ID "PREV_TITULO" already defined
    …sticas.asp' class=modtit>			<span id='prev_titulo'>Brinco</span></a><font clas…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2016, Column 2904: ID "PREV_TEXTO_PRECIO" already defined
    …o</span></a><font class=prc><span id='prev_texto_precio'></span><a href='brinc…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2016, Column 3081: end tag for "FONT" omitted, but its declaration does not permit this
    …l Brinco' border='0'></a>         </td>	    </tr>	   </table>	  </td>      <td…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2016, Column 2878: start tag was here
    …pan id='prev_titulo'>Brinco</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 2016, Column 3156: an attribute value must be a literal unless it contains only name characters
    …<td width='60%'>      <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 3493: an attribute value must be a literal unless it contains only name characters
    …td width='40%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 3575: an attribute value must be a literal unless it contains only name characters
    …   <tr height='25'> 	     <td bgcolor=#F0F0F0><p align='left'>		    <a href='p…

    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.

  • Error Line 2016, Column 3666: ID "PREV_TITULO" already defined
    …sticas.asp' class=modtit>			<span id='prev_titulo'>Poceada</span></a><font cla…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2016, Column 3723: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span><a href='pocea…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2016, Column 3913: end tag for "FONT" omitted, but its declaration does not permit this
    … Poceada' border='0'></a>         </td>	    </tr>	   </table>	  </td>      <td…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2016, Column 3697: start tag was here
    …an id='prev_titulo'>Poceada</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 2016, Column 3988: an attribute value must be a literal unless it contains only name characters
    …<td width='60%'>      <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 4327: an attribute value must be a literal unless it contains only name characters
    …td width='40%'>       <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2016, Column 4409: an attribute value must be a literal unless it contains only name characters
    …   <tr height='25'> 	     <td bgcolor=#F0F0F0><p align='left'>		    <a href='p…

    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.

  • Error Line 2016, Column 4497: ID "PREV_TITULO" already defined
    …sticas.asp' class=modtit>			<span id='prev_titulo'>Qla Plus</span></a><font cl…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2016, Column 4555: ID "PREV_TEXTO_PRECIO" already defined
    …s</span></a><font class=prc><span id='prev_texto_precio'></span><a href='plus_…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2016, Column 4739: end tag for "FONT" omitted, but its declaration does not permit this
    …ela Plus' border='0'></a>         </td>	    </tr>	   </table>	  </td>      <td…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2016, Column 4529: start tag was here
    …n id='prev_titulo'>Qla Plus</span></a><font class=prc><span id='prev_texto_pre…
  • Error Line 2016, Column 4814: an attribute value must be a literal unless it contains only name characters
    …<td width='60%'>      <table width=100% border=0 cellspacing=0 cellpadding=3> …

    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.

  • Error Line 2018, Column 110: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …50" src="Ini_Atras_Abajo_300x250.htm" frameborder="no" scrolling="no"></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 2023, Column 30: document type does not allow element "STYLE" here
           <style type="text/css"><!-- .box {  font-family: Verdana, Arial, Helveti…

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

  • Error Line 2039, Column 91: an attribute value specification must start with a literal or a name character
    … <input type="text" name="usuario" size="12" maxlength="45" class="box" value=>
  • Error Line 2051, Column 89: there is no attribute "WIDTH"
    …lue="Ingresar" src="flecha.gif" width="18" height="19" align="middle" border="…

    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.

  • Error Line 2051, Column 101: there is no attribute "HEIGHT"
    …e="Ingresar" src="flecha.gif" width="18" height="19" align="middle" border="0">

    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.

  • Error Line 2051, Column 128: there is no attribute "BORDER"
    …e="Ingresar" src="flecha.gif" width="18" height="19" align="middle" border="0">

    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.

  • Error Line 2067, Column 30: document type does not allow element "STYLE" here
           <style type="text/css"><!-- .box {  font-family: Verdana, Arial, Helveti…

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

  • Error Line 2113, Column 14: ID "PREV_TITULO" already defined
    			<span id="prev_titulo">Simon </span></a><font class=prc><span id="prev_texto…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2113, Column 70: ID "PREV_TEXTO_PRECIO" already defined
    … </span></a><font class=prc><span id="prev_texto_precio"></span></font><a href…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2114, Column 12: end tag for "FONT" omitted, but its declaration does not permit this
    	      </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2111, Column 44: start tag was here
    …d bgcolor="#F0F0F0"><p align="center"><font face="Verdana, Arial, Helvetica, s…
  • Error Line 2125, Column 14: ID "PREV_TITULO" already defined
    			<span id="prev_titulo">Space Invaders </span></a><font class=prc><span id="p…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2125, Column 79: ID "PREV_TEXTO_PRECIO" already defined
    … </span></a><font class=prc><span id="prev_texto_precio"></span></font><a href…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2127, Column 12: end tag for "FONT" omitted, but its declaration does not permit this
    	      </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2123, Column 44: start tag was here
    …d bgcolor="#F0F0F0"><p align="center"><font face="Verdana, Arial, Helvetica, s…
  • Error Line 2139, Column 14: ID "PREV_TITULO" already defined
    			<span id="prev_titulo">Ta-Te-Ti </span></a><font class=prc><span id="prev_te…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2139, Column 73: ID "PREV_TEXTO_PRECIO" already defined
    … </span></a><font class=prc><span id="prev_texto_precio"></span></font><a href…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2140, Column 12: end tag for "FONT" omitted, but its declaration does not permit this
    	      </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2137, Column 45: start tag was here
    …d bgcolor="#F0F0F0"><p align="center"><font face="Verdana, Arial, Helvetica, s…
  • Error Line 2152, Column 14: ID "PREV_TITULO" already defined
    			<span id="prev_titulo">Tetris </span></a><font class=prc><span id="prev_text…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2152, Column 71: ID "PREV_TEXTO_PRECIO" already defined
    … </span></a><font class=prc><span id="prev_texto_precio"></span></font><a href…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2153, Column 12: end tag for "FONT" omitted, but its declaration does not permit this
    	      </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2150, Column 45: start tag was here
    …d bgcolor="#F0F0F0"><p align="center"><font face="Verdana, Arial, Helvetica, s…
  • Error Line 2166, Column 108: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …c="Ini_Abajo_Der_300x250.htm" frameborder="no" scrolling="no"></iframe>			   		

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 2171, Column 48: literal is missing closing delimiter
    …          <table width="100%" border=" border="3" cellspacing="3"" bordercolor…

    Did you forget to close a (double) quote mark?

  • Error Line 2171, Column 58: character data is not allowed here
    …<table width="100%" border=" border="3" cellspacing="3"" bordercolor="#CC3300"…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2176, Column 61: ID "PREV_TITULO" already defined
    …la_nacional.asp" class="modtit"><span id='prev_titulo'>quinielas</span></a>,   

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2177, Column 60: ID "PREV_TITULO" already defined
    …teria_nacional.asp" class="modtit"><span id='prev_titulo'>loterias</span></a>, 

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2178, Column 54: ID "PREV_TITULO" already defined
    …href="quini6_new.asp" class="modtit"><span id='prev_titulo'>quini 6</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2179, Column 56: ID "PREV_TITULO" already defined
    …f="telekino_new.asp" class="modtit"><span id='prev_titulo'>telekino</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2180, Column 52: ID "PREV_TITULO" already defined
       <a href="loto_new.asp" class="modtit"><span id='prev_titulo'>loto</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2181, Column 53: ID "PREV_TITULO" already defined
    …a href="loto5_new.asp" class="modtit"><span id='prev_titulo'>loto 5</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2182, Column 53: ID "PREV_TITULO" already defined
    …<a href="prode_new.asp" class="modtit"><span id='prev_titulo'>prode</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2183, Column 54: ID "PREV_TITULO" already defined
    … href="brinco_new.asp" class="modtit"><span id='prev_titulo'>brinco</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2184, Column 55: ID "PREV_TITULO" already defined
    …ada_new.asp" class="modtit"><span id='prev_titulo'>quiniela poceada</span></a>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2185, Column 52: ID "PREV_TITULO" already defined
    …="plus_new.asp" class="modtit"><span id='prev_titulo'>quiniela plus</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2186, Column 56: ID "PREV_TITULO" already defined
    …="clubkeno_new.asp" class="modtit"><span id='prev_titulo'>club keno</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2187, Column 55: ID "PREV_TITULO" already defined
    …ef="mibingo_new.asp" class="modtit"><span id='prev_titulo'>mi bingo</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2188, Column 57: ID "PREV_TITULO" already defined
    …monobingo_new.asp" class="modtit"><span id='prev_titulo'>mono bingo</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2189, Column 57: ID "PREV_TITULO" already defined
    …totobingo_new.asp" class="modtit"><span id='prev_titulo'>toto bingo</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2190, Column 56: ID "PREV_TITULO" already defined
    …ona_new.asp" class="modtit"><span id='prev_titulo'>jugá con maradona</span></a…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2191, Column 57: ID "PREV_TITULO" already defined
    …lidaria_new.asp" class="modtit"><span id='prev_titulo'>la solidaria</span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2192, Column 54: ID "PREV_TITULO" already defined
    …el_ruleton.asp" class="modtit"><span id='prev_titulo'>el ruleton</span></a>,   

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2193, Column 52: ID "PREV_TITULO" already defined
    …ozo_new.asp" class="modtit"><span id='prev_titulo'>pozo de la quiniela</span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2195, Column 7: end tag for "FONT" omitted, but its declaration does not permit this
      </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2174, Column 21: start tag was here
      <p align="center"><font Face="Tahoma, Sans-serif" size="2">
  • Error Line 2200, Column 111: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …"250" src="Ini_Abajo_Izq_300x250.htm" frameborder="no" scrolling="no"></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 2205, Column 30: document type does not allow element "STYLE" here
           <style type="text/css"><!-- .box {  font-family: Verdana, Arial, Helveti…

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

  • Error Line 2244, Column 43: literal is missing closing delimiter
    …           <table width="300" border=" border="3" cellspacing="3" bordercolor=…

    Did you forget to close a (double) quote mark?

  • Error Line 2244, Column 53: character data is not allowed here
    … <table width="300" border=" border="3" cellspacing="3" bordercolor="#CC3300" …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2249, Column 103: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>Florida Lotto</b></span>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2250, Column 102: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>Euromillones</b></span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2251, Column 101: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>France Loto</b></span></…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2252, Column 99: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>PowerBall</b></span></a>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2253, Column 98: ID "PREV_TITULO" already defined
    …en_linea.asp" class="modtit"><span id='prev_titulo'><b>Oz Lotto</b></span></a>,

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2254, Column 99: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>Mega Sena</b></span></a>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2255, Column 105: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>Megamillions</b></span><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2256, Column 98: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>El Gordo de la Primitiva…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2257, Column 104: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>Super EnaLotto</b></span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2258, Column 109: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>UK National Lottery</b><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2259, Column 104: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>New York Lotto</b></span…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2260, Column 109: ID "PREV_TITULO" already defined
    …n_linea.asp" class="modtit"><span id='prev_titulo'><b>California Super Lotto</…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2268, Column 673: ID "PREV_TITULO" already defined
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Lotería Nacional</span></a>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2268, Column 739: ID "PREV_TEXTO_PRECIO" already defined
    …l</span></a><font class=prc><span id='prev_texto_precio'></span></font><a href…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2268, Column 1282: end tag for "FONT" omitted, but its declaration does not permit this
    …<b>La Lavandera </b></font>	      </td>	    </tr>	   </table>	  </td>	 </tr>  …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2268, Column 549: start tag was here
    …d bgcolor='#FFFFF0'><p align='center'><font face='Verdana, Arial, Helvetica, s…
  • Error Line 2268, Column 1582: ID "PREV_TITULO" already defined
    …aires.asp' class=modtit> 			<span id='prev_titulo'>Lotería Buenos Aires</span>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2268, Column 1652: ID "PREV_TEXTO_PRECIO" already defined
    …s</span></a><font class=prc><span id='prev_texto_precio'></span></font><a href…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2268, Column 2211: end tag for "FONT" omitted, but its declaration does not permit this
    …b>El Casamiento </b></font>	      </td>	    </tr>	   </table>	  </td>	 </tr>  …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2268, Column 1455: start tag was here
    …d bgcolor='#FFFFF0'><p align='center'><font face='Verdana, Arial, Helvetica, s…
  • Error Line 2268, Column 2513: ID "PREV_TITULO" already defined
    …rdoba.asp' class=modtit> 			<span id='prev_titulo'>Lotería Córdoba</span></a><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2268, Column 2578: ID "PREV_TEXTO_PRECIO" already defined
    …a</span></a><font class=prc><span id='prev_texto_precio'></span></font><a href…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2268, Column 3123: end tag for "FONT" omitted, but its declaration does not permit this
    …<b>La Desgracia </b></font>	      </td>        </tr>       </table>      </td>…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2268, Column 2386: start tag was here
    …d bgcolor='#FFFFF0'><p align='center'><font face='Verdana, Arial, Helvetica, s…
  • Error Line 2268, Column 3437: ID "PREV_TITULO" already defined
    …ntafe.asp' class=modtit> 			<span id='prev_titulo'>Lotería Santa Fé</span></a>…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2268, Column 3503: ID "PREV_TEXTO_PRECIO" already defined
    …é</span></a><font class=prc><span id='prev_texto_precio'></span></font><a href…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2268, Column 4042: end tag for "FONT" omitted, but its declaration does not permit this
    …8000'><b>El pan </b></font>	      </td>        </tr>       </table>      </td>…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2268, Column 3310: start tag was here
    …d bgcolor='#FFFFF0'><p align='center'><font face='Verdana, Arial, Helvetica, s…
  • Error Line 2268, Column 4358: ID "PREV_TITULO" already defined
    …icada.asp' class=modtit> 			<span id='prev_titulo'>Lotería Neuquen</span></a><…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2268, Column 4423: ID "PREV_TEXTO_PRECIO" already defined
    …n</span></a><font class=prc><span id='prev_texto_precio'></span></font><a href…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2268, Column 4963: end tag for "FONT" omitted, but its declaration does not permit this
    …8000'><b>La luz </b></font>	      </td>        </tr>       </table>      </td>…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2268, Column 4229: start tag was here
    …d bgcolor='#FFFFF0'><p align='center'><font face='Verdana, Arial, Helvetica, s…
  • Error Line 2268, Column 5278: ID "PREV_TITULO" already defined
    …tiago.asp' class=modtit> 			<span id='prev_titulo'>Lotería Santiago del Estero…

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

  • Info Line 644, Column 1318: ID "PREV_TITULO" first defined here
    …ional.asp' class=modtit> 			<span id='prev_titulo'>Quiniela <br>Nacional</span…
  • Error Line 2268, Column 5355: ID "PREV_TEXTO_PRECIO" already defined
    …o</span></a><font class=prc><span id='prev_texto_precio'></span></font><a href…

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

  • Info Line 644, Column 1389: ID "PREV_TEXTO_PRECIO" first defined here
    …l</span></a><font class=prc><span id='prev_texto_precio'></span><a href='quini…
  • Error Line 2268, Column 5908: end tag for "FONT" omitted, but its declaration does not permit this
    …000'><b>El Humo </b></font>	      </td>        </tr>       </table>      </td>…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2268, Column 5150: start tag was here
    …d bgcolor='#FFFFF0'><p align='center'><font face='Verdana, Arial, Helvetica, s…
  • Error Line 2276, Column 56: document type does not allow element "TD" here
                 <td valign="top" align="center" width="2%">

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

  • Error Line 2280, Column 19: end tag for element "TR" which is not open
                  </tr>

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

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

  • Error Line 2281, Column 20: end tag for element "TABLE" which is not open
                </table>

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

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

  • Error Line 2282, Column 16: end tag for "CENTER" omitted, but its declaration does not permit this
              </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1191, Column 3: start tag was here
      <center>
  • Error Line 2283, Column 13: end tag for element "TD" which is not open
            </td>

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

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

  • Error Line 2285, Column 52: document type does not allow element "TD" here
            <td width="18%" valign="top" align="center">

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

  • Error Line 2292, Column 106: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …"600" src="Ini_Der_Abajo_160x600.htm" frameborder="no" scrolling="no"></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 2294, Column 43: required attribute "TYPE" not specified
     		          <script language="JavaScript">

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

  • Warning Line 2315, Column 171: unclosed start-tag requires SHORTTAG YES
    …new1.gif" alt="Euromillones: Combinación ganadora del sorteo: Euromillones"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2324, Column 170: unclosed start-tag requires SHORTTAG YES
    …w1.gif" alt="La Primitiva: Combinación ganadora del sorteo de La Primitiva"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2333, Column 155: unclosed start-tag requires SHORTTAG YES
    …0" src="new1.gif" alt="Bono Loto: Combinación ganadora del sorteo Bonoloto"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2341, Column 160: unclosed start-tag requires SHORTTAG YES
    … src="new1.gif" alt="El Quinigol: Combinación ganadora del sorteo Quinigol"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2350, Column 185: unclosed start-tag requires SHORTTAG YES
    … de la Primitiva: Combinación ganadora del sorteo El Gordo de la Primitiva"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2359, Column 192: unclosed start-tag requires SHORTTAG YES
    …="Loteria Nacional: Combinación ganadora del sorteo de la Lotería Nacional"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2367, Column 175: unclosed start-tag requires SHORTTAG YES
    …" alt="La Quiniela 1x2: Combinación ganadora del sorteo de La Quiniela 1x2"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2375, Column 178: unclosed start-tag requires SHORTTAG YES
    …1.gif" alt="Quintuple Plus: Combinación ganadora del sorteo Quintuple Plus"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2383, Column 157: unclosed start-tag requires SHORTTAG YES
    …" src="new1.gif" alt="Lototurf: Combinación ganadora del sorteo: Loto Turf"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2391, Column 149: unclosed start-tag requires SHORTTAG YES
    …r="0" src="new1.gif" alt="La once: Combinación ganadora del sorteo La Once"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2418, Column 177: unclosed start-tag requires SHORTTAG YES
    …ate tradicional y Melate Revancha: Resultados del sorteo Melate y revancha"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2427, Column 124: unclosed start-tag requires SHORTTAG YES
    …">&nbsp;Melate Retro&nbsp;<img border="0" src="new1.gif" alt="Melate Retro"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2436, Column 136: unclosed start-tag requires SHORTTAG YES
    …p;<img border="0" src="new1.gif" alt="Progol: Resultados del sorteo Progol"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2444, Column 174: unclosed start-tag requires SHORTTAG YES
    …1.gif" alt="Progol: Resultados del sorteo Progol 1/2 semana - media semana"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2454, Column 192: unclosed start-tag requires SHORTTAG YES
    …ganador: Resultados del sorteo Chispazo tradicinal y chispazo Multiganador"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2464, Column 149: unclosed start-tag requires SHORTTAG YES
    … border="0" src="new1.gif" alt="Gana Gato: Resultados del sorteo Gana Gato"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2472, Column 149: unclosed start-tag requires SHORTTAG YES
    …der="0" src="new1.gif" alt="Piensa Tris: Resultados del sorteo Piensa Tris"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Warning Line 2481, Column 144: unclosed start-tag requires SHORTTAG YES
    …mg border="0" src="new1.gif" alt="Protouch: Resultados del sorteo Protouch"</a>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Error Line 2581, Column 107: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …600" src="Ini_Der_Abajo2_160x600.htm" frameborder="no" scrolling="no"></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 2590, Column 10: end tag for element "TR" which is not open
         </tr>

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

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

  • Error Line 2591, Column 10: end tag for element "TABLE" which is not open
      </table>

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

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

  • Error Line 2592, Column 11: end tag for element "CENTER" which is not open
      </center>

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

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

  • Error Line 2593, Column 6: end tag for element "DIV" which is not open
    </div>

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

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

  • Error Line 2608, Column 113: value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0"
    …0_R0.htm" id="frame5" name="frame5" frameborder="no" scrolling="no"></iframe>  

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 2624, Column 18: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
           <td align=middle bgcolor=#99CCCC><font color=#ffffff 

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 2624, Column 33: an attribute value must be a literal unless it contains only name characters
           <td align=middle bgcolor=#99CCCC><font color=#ffffff 

    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.

  • Error Line 2624, Column 53: an attribute value must be a literal unless it contains only name characters
           <td align=middle bgcolor=#99CCCC><font color=#ffffff 

    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.

  • Error Line 2639, Column 38: required attribute "ALT" not specified
              src="1x1redh.gif" width=470>

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

  • Error Line 2643, Column 13: end tag for "FONT" omitted, but its declaration does not permit this
            </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 2641, Column 36: start tag was here
            <td align="left" width=123><font face="Verdana, Arial, Helvetica" 
  • Error Line 2654, Column 21: an attribute value must be a literal unless it contains only name characters
            <font color=#8b8b8b face="Verdana, Arial, Helvetica" size=-2>Copyright 

    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.

Visitor Analysis

Daily Visitor
  • 5.950 visits