tunisia-sat.com

المنتدى العربي الأول في عالم الساتلايت و التكنولوجيا والانترنات * High Tech, Satellite, Mobile, Movies and Computers Best Arabic Multilingual Board ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    tunisia-sat.com
  • Favicon
  • Alexa Rank
    #3544
  • Google Page Rank
    PR 2
  • Ip Address
    190.93.240.31
  • Page Size
    186.9 KB
  • Images
    248 GIF, 6 JPG, 47 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    منتديات تونيزيـا سات - Tunisia-Sat Forums
  • Meta Keyword
    Digital satellite, tunisia discussion, tunisia classifieds, tunisia job search, annonces tunisie, emploi tunisie, voyage tunisie, travel tunisia,skystar,topnet, orange tunisie, tunisie telecom, tunisie 3g,hdtv, vuplus ,internet tv,dreambox, satellite dish,DiseqC, router network,voip,starsat, samsat, startrack, nokia nseries,iphone jailbreak,ipad,network camera,ps3,dm500s ,dm800, satellite tv,digital receiver,encryption,console jeux, tunisia news, nouvelles tunisie, actualité tunisie, sport tunisie, championnat football tunisie, offres emploi tunisie, vente achat tunisie, revolution tunisie, أجهزة, برامج, tunisie revolution, الثورة التونسية
  • Meta Description
    المنتدى العربي الأول في عالم الساتلايت و التكنولوجيا والانترنات * High Tech, Satellite, Mobile, Movies and Computers Best Arabic Multilingual Board

Technical Analysis



  • Webserver
    cloudflare-nginx
  • Ip Address
    190.93.240.31
  • Domain Age
    7 Years, 6 Months, 5 days.
  • Javascript Library
    yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from tunisia-sat.com.

HTML Analysis

  • server: cloudflare-nginx
  • date: Fri, 26 Apr 2013 01:20:11 GMT
  • content-type: text/html; charset=windows-1256
  • connection: keep-alive
  • x-powered-by: PHP/5.3.24
  • cache-control: private
  • pragma: private
  • vary: User-Agent,Accept-Encoding
  • cf-ray: 64f72f176f00443
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: tunisia-sat.com

Registrant Contact:
WhoisGuard
WhoisGuard Protected ()

Fax:
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Administrative Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Technical Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Status: Active

Name Servers:
carl.ns.cloudflare.com
pat.ns.cloudflare.com

Creation date: 29 Oct 2005 01:00:13
Expiration date: 29 Oct 2013 01:00:00

DNS Analysis


DNS servers
carl.ns.cloudflare.com [173.245.59.106]
pat.ns.cloudflare.com [173.245.58.139]

DNS Records

Answer records
tunisia-sat.com A 108.162.207.76 300s
tunisia-sat.com A 108.162.201.77 300s
tunisia-sat.com A 141.101.127.76 300s
tunisia-sat.com A 108.162.202.77 300s
tunisia-sat.com SOA
server: carl.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2012102314
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
tunisia-sat.com MX
preference: 10
exchange: ASPMX3.GOOGLEMAIL.com
300s
tunisia-sat.com NS  carl.ns.cloudflare.com 86400s
tunisia-sat.com MX
preference: 0
exchange: ASPMX.L.GOOGLE.com
300s
tunisia-sat.com MX
preference: 5
exchange: ALT1.ASPMX.L.GOOGLE.com
300s
tunisia-sat.com A 108.162.200.77 300s
tunisia-sat.com MX
preference: 10
exchange: ASPMX2.GOOGLEMAIL.com
300s
tunisia-sat.com NS  pat.ns.cloudflare.com 86400s
tunisia-sat.com MX
preference: 5
exchange: ALT2.ASPMX.L.GOOGLE.com
300s

Authority records

Additional records

IP 190.93.240.31 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 258 Errors
  • 50 Warnings
Ratio Text/Html
  • 0.6379348189647964
Message Error
  • Error Line 16, Column 11: there is no attribute "REL"
    <link REL="SHORTCUT ICON" HREF="fav.ico">

    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 16, Column 32: there is no attribute "HREF"
    <link REL="SHORTCUT ICON" HREF="fav.ico">

    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 16, Column 42: end tag for "link" omitted, but OMITTAG NO was specified
    <link REL="SHORTCUT ICON" HREF="fav.ico">

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

  • Info Line 16, Column 1: start tag was here
    <link REL="SHORTCUT ICON" HREF="fav.ico">
  • Error Line 134, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 138, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=365884483484830";

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 138, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=365884483484830";

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

  • Warning Line 138, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=365884483484830";

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

  • Error Line 138, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=365884483484830";

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

  • Info Line 138, Column 56: entity was defined here
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=365884483484830";
  • Error Line 147, Column 20: document type does not allow element "div" here
    <div 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 255, Column 45: there is no attribute "data-href"
    …lign="left" class="fb-like" data-href="https://www.facebook.com/tunisiasat.off…

    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 255, Column 102: there is no attribute "data-send"
    …ok.com/tunisiasat.official" data-send="false" data-width="450" data-show-faces…

    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 255, Column 121: there is no attribute "data-width"
    …fficial" data-send="false" data-width="450" data-show-faces="false" data-font=…

    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 255, Column 143: there is no attribute "data-show-faces"
    …send="false" data-width="450" data-show-faces="false" data-font="tahoma"></div>

    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 255, Column 161: there is no attribute "data-font"
    …send="false" data-width="450" data-show-faces="false" data-font="tahoma"></div>

    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 297, Column 55: element "STRONG" undefined
    وكيفية تعاملك معها نوصيك وبشده التوجه الى صفحة <STRONG>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 300, Column 32: element "BR" undefined
    عليها بشأن استخدام المنتدى .<BR>أما إذا كنت تود الانضمام إلى اسرتنا يتوجب عليك …

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 300, Column 87: element "STRONG" undefined
    …أن استخدام المنتدى .<BR>أما إذا كنت تود الانضمام إلى اسرتنا يتوجب عليك <STRONG>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 301, Column 60: end tag for element "strong" which is not open
    <a href="register.php">&nbsp;التسجيل بالضغط هنا</a></strong> 

    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 302, Column 6: end tag for "STRONG" omitted, but OMITTAG NO was specified
    	</td>

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

  • Info Line 300, Column 80: start tag was here
    …أن استخدام المنتدى .<BR>أما إذا كنت تود الانضمام إلى اسرتنا يتوجب عليك <STRONG>
  • Error Line 302, Column 6: end tag for "BR" omitted, but OMITTAG NO was specified
    	</td>

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

  • Info Line 300, Column 29: start tag was here
    عليها بشأن استخدام المنتدى .<BR>أما إذا كنت تود الانضمام إلى اسرتنا يتوجب عليك …
  • Error Line 377, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">259.461</td></font>

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

  • Info Line 377, Column 19: start tag was here
    	<td class="alt1"><font size="2">259.461</td></font>
  • Error Line 377, Column 52: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">259.461</td></font>

    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 378, Column 47: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">2.046.988</td></font>

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

  • Info Line 378, Column 19: start tag was here
    	<td class="alt2"><font size="2">2.046.988</td></font>
  • Error Line 378, Column 54: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">2.046.988</td></font>

    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 413, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">44.064</td></font>

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

  • Info Line 413, Column 19: start tag was here
    	<td class="alt1"><font size="2">44.064</td></font>
  • Error Line 413, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">44.064</td></font>

    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 414, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">242.509</td></font>

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

  • Info Line 414, Column 19: start tag was here
    	<td class="alt2"><font size="2">242.509</td></font>
  • Error Line 414, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">242.509</td></font>

    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 449, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">17.348</td></font>

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

  • Info Line 449, Column 19: start tag was here
    	<td class="alt1"><font size="2">17.348</td></font>
  • Error Line 449, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">17.348</td></font>

    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 450, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">121.545</td></font>

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

  • Info Line 450, Column 19: start tag was here
    	<td class="alt2"><font size="2">121.545</td></font>
  • Error Line 450, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">121.545</td></font>

    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 485, Column 43: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">1.873</td></font>

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

  • Info Line 485, Column 19: start tag was here
    	<td class="alt1"><font size="2">1.873</td></font>
  • Error Line 485, Column 50: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">1.873</td></font>

    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 486, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">10.328</td></font>

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

  • Info Line 486, Column 19: start tag was here
    	<td class="alt2"><font size="2">10.328</td></font>
  • Error Line 486, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">10.328</td></font>

    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 521, Column 43: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">7.715</td></font>

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

  • Info Line 521, Column 19: start tag was here
    	<td class="alt1"><font size="2">7.715</td></font>
  • Error Line 521, Column 50: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">7.715</td></font>

    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 522, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">37.559</td></font>

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

  • Info Line 522, Column 19: start tag was here
    	<td class="alt2"><font size="2">37.559</td></font>
  • Error Line 522, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">37.559</td></font>

    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 557, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">14.944</td></font>

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

  • Info Line 557, Column 19: start tag was here
    	<td class="alt1"><font size="2">14.944</td></font>
  • Error Line 557, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">14.944</td></font>

    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 558, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">102.039</td></font>

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

  • Info Line 558, Column 19: start tag was here
    	<td class="alt2"><font size="2">102.039</td></font>
  • Error Line 558, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">102.039</td></font>

    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 593, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">54.298</td></font>

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

  • Info Line 593, Column 19: start tag was here
    	<td class="alt1"><font size="2">54.298</td></font>
  • Error Line 593, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">54.298</td></font>

    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 594, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">399.476</td></font>

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

  • Info Line 594, Column 19: start tag was here
    	<td class="alt2"><font size="2">399.476</td></font>
  • Error Line 594, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">399.476</td></font>

    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 665, Column 43: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">5.723</td></font>

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

  • Info Line 665, Column 19: start tag was here
    	<td class="alt1"><font size="2">5.723</td></font>
  • Error Line 665, Column 50: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">5.723</td></font>

    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 666, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">41.508</td></font>

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

  • Info Line 666, Column 19: start tag was here
    	<td class="alt2"><font size="2">41.508</td></font>
  • Error Line 666, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">41.508</td></font>

    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 701, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">45.844</td></font>

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

  • Info Line 701, Column 19: start tag was here
    	<td class="alt1"><font size="2">45.844</td></font>
  • Error Line 701, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">45.844</td></font>

    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 702, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">217.914</td></font>

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

  • Info Line 702, Column 19: start tag was here
    	<td class="alt2"><font size="2">217.914</td></font>
  • Error Line 702, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">217.914</td></font>

    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 737, Column 43: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">6.849</td></font>

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

  • Info Line 737, Column 19: start tag was here
    	<td class="alt1"><font size="2">6.849</td></font>
  • Error Line 737, Column 50: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">6.849</td></font>

    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 738, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">37.041</td></font>

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

  • Info Line 738, Column 19: start tag was here
    	<td class="alt2"><font size="2">37.041</td></font>
  • Error Line 738, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">37.041</td></font>

    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 773, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">20.511</td></font>

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

  • Info Line 773, Column 19: start tag was here
    	<td class="alt1"><font size="2">20.511</td></font>
  • Error Line 773, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">20.511</td></font>

    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 774, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">82.459</td></font>

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

  • Info Line 774, Column 19: start tag was here
    	<td class="alt2"><font size="2">82.459</td></font>
  • Error Line 774, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">82.459</td></font>

    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 809, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">21.060</td></font>

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

  • Info Line 809, Column 19: start tag was here
    	<td class="alt1"><font size="2">21.060</td></font>
  • Error Line 809, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">21.060</td></font>

    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 810, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">89.330</td></font>

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

  • Info Line 810, Column 19: start tag was here
    	<td class="alt2"><font size="2">89.330</td></font>
  • Error Line 810, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">89.330</td></font>

    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 885, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">19.932</td></font>

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

  • Info Line 885, Column 19: start tag was here
    	<td class="alt1"><font size="2">19.932</td></font>
  • Error Line 885, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">19.932</td></font>

    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 886, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">103.423</td></font>

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

  • Info Line 886, Column 19: start tag was here
    	<td class="alt2"><font size="2">103.423</td></font>
  • Error Line 886, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">103.423</td></font>

    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 925, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">172.419</td></font>

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

  • Info Line 925, Column 19: start tag was here
    	<td class="alt1"><font size="2">172.419</td></font>
  • Error Line 925, Column 52: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">172.419</td></font>

    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 926, Column 47: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">1.262.649</td></font>

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

  • Info Line 926, Column 19: start tag was here
    	<td class="alt2"><font size="2">1.262.649</td></font>
  • Error Line 926, Column 54: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">1.262.649</td></font>

    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 961, Column 43: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">6.439</td></font>

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

  • Info Line 961, Column 19: start tag was here
    	<td class="alt1"><font size="2">6.439</td></font>
  • Error Line 961, Column 50: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">6.439</td></font>

    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 962, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">44.776</td></font>

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

  • Info Line 962, Column 19: start tag was here
    	<td class="alt2"><font size="2">44.776</td></font>
  • Error Line 962, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">44.776</td></font>

    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 1037, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">81.243</td></font>

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

  • Info Line 1037, Column 19: start tag was here
    	<td class="alt1"><font size="2">81.243</td></font>
  • Error Line 1037, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">81.243</td></font>

    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 1038, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">502.304</td></font>

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

  • Info Line 1038, Column 19: start tag was here
    	<td class="alt2"><font size="2">502.304</td></font>
  • Error Line 1038, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">502.304</td></font>

    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 1077, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">68.248</td></font>

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

  • Info Line 1077, Column 19: start tag was here
    	<td class="alt1"><font size="2">68.248</td></font>
  • Error Line 1077, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">68.248</td></font>

    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 1078, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">326.570</td></font>

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

  • Info Line 1078, Column 19: start tag was here
    	<td class="alt2"><font size="2">326.570</td></font>
  • Error Line 1078, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">326.570</td></font>

    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 1149, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">35.843</td></font>

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

  • Info Line 1149, Column 19: start tag was here
    	<td class="alt1"><font size="2">35.843</td></font>
  • Error Line 1149, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">35.843</td></font>

    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 1150, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">204.279</td></font>

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

  • Info Line 1150, Column 19: start tag was here
    	<td class="alt2"><font size="2">204.279</td></font>
  • Error Line 1150, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">204.279</td></font>

    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 1165, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">31.028</td></font>

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

  • Info Line 1165, Column 19: start tag was here
    	<td class="alt1"><font size="2">31.028</td></font>
  • Error Line 1165, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">31.028</td></font>

    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 1166, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">192.855</td></font>

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

  • Info Line 1166, Column 19: start tag was here
    	<td class="alt2"><font size="2">192.855</td></font>
  • Error Line 1166, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">192.855</td></font>

    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 1201, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">16.952</td></font>

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

  • Info Line 1201, Column 19: start tag was here
    	<td class="alt1"><font size="2">16.952</td></font>
  • Error Line 1201, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">16.952</td></font>

    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 1202, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">102.728</td></font>

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

  • Info Line 1202, Column 19: start tag was here
    	<td class="alt2"><font size="2">102.728</td></font>
  • Error Line 1202, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">102.728</td></font>

    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 1237, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">15.496</td></font>

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

  • Info Line 1237, Column 19: start tag was here
    	<td class="alt1"><font size="2">15.496</td></font>
  • Error Line 1237, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">15.496</td></font>

    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 1238, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">99.239</td></font>

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

  • Info Line 1238, Column 19: start tag was here
    	<td class="alt2"><font size="2">99.239</td></font>
  • Error Line 1238, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">99.239</td></font>

    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 1253, Column 43: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">4.841</td></font>

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

  • Info Line 1253, Column 19: start tag was here
    	<td class="alt1"><font size="2">4.841</td></font>
  • Error Line 1253, Column 50: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">4.841</td></font>

    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 1254, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">24.643</td></font>

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

  • Info Line 1254, Column 19: start tag was here
    	<td class="alt2"><font size="2">24.643</td></font>
  • Error Line 1254, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">24.643</td></font>

    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 1325, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">30.073</td></font>

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

  • Info Line 1325, Column 19: start tag was here
    	<td class="alt1"><font size="2">30.073</td></font>
  • Error Line 1325, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">30.073</td></font>

    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 1326, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">158.362</td></font>

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

  • Info Line 1326, Column 19: start tag was here
    	<td class="alt2"><font size="2">158.362</td></font>
  • Error Line 1326, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">158.362</td></font>

    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 1361, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">10.851</td></font>

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

  • Info Line 1361, Column 19: start tag was here
    	<td class="alt1"><font size="2">10.851</td></font>
  • Error Line 1361, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">10.851</td></font>

    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 1362, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">52.615</td></font>

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

  • Info Line 1362, Column 19: start tag was here
    	<td class="alt2"><font size="2">52.615</td></font>
  • Error Line 1362, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">52.615</td></font>

    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 1397, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">68.454</td></font>

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

  • Info Line 1397, Column 19: start tag was here
    	<td class="alt1"><font size="2">68.454</td></font>
  • Error Line 1397, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">68.454</td></font>

    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 1398, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">421.438</td></font>

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

  • Info Line 1398, Column 19: start tag was here
    	<td class="alt2"><font size="2">421.438</td></font>
  • Error Line 1398, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">421.438</td></font>

    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 1437, Column 41: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">166</td></font>

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

  • Info Line 1437, Column 19: start tag was here
    	<td class="alt1"><font size="2">166</td></font>
  • Error Line 1437, Column 48: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">166</td></font>

    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 1438, Column 41: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">753</td></font>

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

  • Info Line 1438, Column 19: start tag was here
    	<td class="alt2"><font size="2">753</td></font>
  • Error Line 1438, Column 48: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">753</td></font>

    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 1473, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">15.267</td></font>

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

  • Info Line 1473, Column 19: start tag was here
    	<td class="alt1"><font size="2">15.267</td></font>
  • Error Line 1473, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">15.267</td></font>

    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 1474, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">112.579</td></font>

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

  • Info Line 1474, Column 19: start tag was here
    	<td class="alt2"><font size="2">112.579</td></font>
  • Error Line 1474, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">112.579</td></font>

    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 1509, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">44.328</td></font>

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

  • Info Line 1509, Column 19: start tag was here
    	<td class="alt1"><font size="2">44.328</td></font>
  • Error Line 1509, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">44.328</td></font>

    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 1510, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">218.016</td></font>

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

  • Info Line 1510, Column 19: start tag was here
    	<td class="alt2"><font size="2">218.016</td></font>
  • Error Line 1510, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">218.016</td></font>

    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 1545, Column 43: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">4.057</td></font>

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

  • Info Line 1545, Column 19: start tag was here
    	<td class="alt1"><font size="2">4.057</td></font>
  • Error Line 1545, Column 50: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">4.057</td></font>

    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 1546, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">14.251</td></font>

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

  • Info Line 1546, Column 19: start tag was here
    	<td class="alt2"><font size="2">14.251</td></font>
  • Error Line 1546, Column 51: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">14.251</td></font>

    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 1581, Column 43: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">2.217</td></font>

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

  • Info Line 1581, Column 19: start tag was here
    	<td class="alt1"><font size="2">2.217</td></font>
  • Error Line 1581, Column 50: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">2.217</td></font>

    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 1582, Column 43: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">8.666</td></font>

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

  • Info Line 1582, Column 19: start tag was here
    	<td class="alt2"><font size="2">8.666</td></font>
  • Error Line 1582, Column 50: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">8.666</td></font>

    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 1653, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">215.388</td></font>

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

  • Info Line 1653, Column 19: start tag was here
    	<td class="alt1"><font size="2">215.388</td></font>
  • Error Line 1653, Column 52: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">215.388</td></font>

    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 1654, Column 47: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">1.118.735</td></font>

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

  • Info Line 1654, Column 19: start tag was here
    	<td class="alt2"><font size="2">1.118.735</td></font>
  • Error Line 1654, Column 54: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">1.118.735</td></font>

    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 1693, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">86.849</td></font>

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

  • Info Line 1693, Column 19: start tag was here
    	<td class="alt1"><font size="2">86.849</td></font>
  • Error Line 1693, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">86.849</td></font>

    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 1694, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">483.938</td></font>

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

  • Info Line 1694, Column 19: start tag was here
    	<td class="alt2"><font size="2">483.938</td></font>
  • Error Line 1694, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">483.938</td></font>

    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 1729, Column 44: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt1"><font size="2">65.116</td></font>

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

  • Info Line 1729, Column 19: start tag was here
    	<td class="alt1"><font size="2">65.116</td></font>
  • Error Line 1729, Column 51: end tag for element "font" which is not open
    	<td class="alt1"><font size="2">65.116</td></font>

    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 1730, Column 45: end tag for "font" omitted, but OMITTAG NO was specified
    	<td class="alt2"><font size="2">324.762</td></font>

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

  • Info Line 1730, Column 19: start tag was here
    	<td class="alt2"><font size="2">324.762</td></font>
  • Error Line 1730, Column 52: end tag for element "font" which is not open
    	<td class="alt2"><font size="2">324.762</td></font>

    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 1780, Column 7: document type does not allow element "br" here; missing one of "th", "td" start-tag
    		<br/>

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

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

  • Error Line 1781, Column 6: end tag for "tr" which is not finished
    	</tr>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 1782, Column 8: end tag for element "tbody" which is not open
    </tbody>

    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 1785, Column 7: document type does not allow element "tbody" here
    <tbody>

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1793, Column 53: document type does not allow element "tbody" here
    <tbody id="collapseobj_forumhome_birthdays" style="">

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

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

  • Error Line 1812, Column 19: document type does not allow element "div" here; missing one of "th", "td" start-tag
    <div id="sideicon">

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

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

  • Error Line 1845, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1845, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1845, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1850, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1850, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1850, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1855, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1855, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1855, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1860, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1860, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1860, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1865, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1865, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1865, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1870, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1870, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1870, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1875, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1875, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1875, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1880, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1880, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1880, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1885, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1885, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1885, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1890, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1890, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1890, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1895, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1895, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1895, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1900, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1900, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1900, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1905, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1905, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1905, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1910, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1910, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1910, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1915, Column 108: required attribute "alt" not specified
    …astpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacf…

    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 1915, Column 109: end tag for "img" omitted, but OMITTAG NO was specified
    …stpost.gif" border="0" align="middle">&nbsp;<a href="showthread.php?s=122eacfe…

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

  • Info Line 1915, Column 32: start tag was here
            <div class="smallfont"><img src="images/styles/TSBB/buttons/lastpost.gi…
  • Error Line 1920, Column 19: document type does not allow element "tr" here; assuming missing "tbody" start-tag
    	<tr class="tfoot">
  • Error Line 1923, Column 8: end tag for "tbody" omitted, but OMITTAG NO was specified
    </table><br /></td></tr>

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

  • Info Line 1920, Column 2: start tag was here
    	<tr class="tfoot">
  • Error Line 1930, Column 75: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ebook.com/tunisiasat.official" target=_blank"><img src="images/misc/icons/face…
  • Error Line 1930, Column 81: an attribute specification must start with a name or name token
    …com/tunisiasat.official" target=_blank"><img src="images/misc/icons/facebook.p…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1930, Column 168: end tag for "img" omitted, but OMITTAG NO was specified
    …ages/misc/icons/facebook.png" border="0" alt="Facebook Official Page"></a></td>

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

  • Info Line 1930, Column 83: start tag was here
    …m/tunisiasat.official" target=_blank"><img src="images/misc/icons/facebook.png…
  • Error Line 1931, Column 83: end tag for "img" omitted, but OMITTAG NO was specified
    …    <td><img src="images/misc/icons/twitter.png" border="0" alt="Twitter"></td>

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

  • Info Line 1931, Column 13: start tag was here
            <td><img src="images/misc/icons/twitter.png" border="0" alt="Twitter"><…
  • Error Line 1932, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …  <td><img src="images/misc/icons/linkedin.png" border="0" alt="LinkedIn"></td>

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

  • Info Line 1932, Column 13: start tag was here
            <td><img src="images/misc/icons/linkedin.png" border="0" alt="LinkedIn"…
  • Error Line 1933, Column 87: end tag for "img" omitted, but OMITTAG NO was specified
    …<td><img src="images/misc/icons/google_plus.png" border="0" alt="Google+"></td>

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

  • Info Line 1933, Column 13: start tag was here
            <td><img src="images/misc/icons/google_plus.png" border="0" alt="Google…
  • Error Line 2008, Column 8: end tag for element "tbody" which is not open
    </tbody>

    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 2027, Column 254: end tag for "img" omitted, but OMITTAG NO was specified
    …ges/misc/icons/general_bw.jpg'" title="" border="0" alt="القسم العام"></a></td>

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

  • Info Line 2027, Column 57: start tag was here
    …"50%"><a href="forumdisplay.php?f=88"><img src="images/misc/icons/general_bw.j…
  • Error Line 2028, Column 276: end tag for "img" omitted, but OMITTAG NO was specified
    …e_bw.jpg'" title="" border="0" alt="قسم التعليم والعلوم والتكنولوجيا"></a></td>

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

  • Info Line 2028, Column 58: start tag was here
    …50%"><a href="forumdisplay.php?f=418"><img src="images/misc/icons/science_bw.j…
  • Error Line 2033, Column 267: end tag for "img" omitted, but OMITTAG NO was specified
    …k_bw.jpg'" title="" border="0" alt="قسم الشغل والمعاملات الإلكترونية"></a></td>

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

  • Info Line 2033, Column 58: start tag was here
    …50%"><a href="forumdisplay.php?f=376"><img src="images/misc/icons/work_bw.jpg"…
  • Error Line 2034, Column 260: end tag for "img" omitted, but OMITTAG NO was specified
    …/icons/cinema_bw.jpg'" title="" border="0" alt="قسم السينما والاغاني"></a></td>

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

  • Info Line 2034, Column 57: start tag was here
    …"50%"><a href="forumdisplay.php?f=90"><img src="images/misc/icons/cinema_bw.jp…
  • Error Line 2038, Column 261: end tag for "img" omitted, but OMITTAG NO was specified
    …misc/icons/satellite_bw.jpg'" title="" border="0" alt="قسم الفضائيات"></a></td>

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

  • Info Line 2038, Column 56: start tag was here
    …="50%"><a href="forumdisplay.php?f=3"><img src="images/misc/icons/satellite_bw…
  • Error Line 2039, Column 298: end tag for "img" omitted, but OMITTAG NO was specified
    …"" border="0" alt="قسم الكمبيوتر والجوالات وتطوير المواقع والمنتديات"></a></td>

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

  • Info Line 2039, Column 57: start tag was here
    …"50%"><a href="forumdisplay.php?f=41"><img src="images/misc/icons/computers_bw…
  • Warning Line 2048, Column 75: cannot generate system identifier for general entity "f"
    …sat.com/vb/newthread.php?do=newthread&f=283"><img src="images/misc/adbox-left.…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2048, Column 75: general entity "f" not defined and no default entity
    …sat.com/vb/newthread.php?do=newthread&f=283"><img src="images/misc/adbox-left.…

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

  • Warning Line 2048, Column 76: reference not terminated by REFC delimiter
    …at.com/vb/newthread.php?do=newthread&f=283"><img src="images/misc/adbox-left.g…

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

  • Warning Line 2048, Column 76: reference to external entity in attribute value
    …at.com/vb/newthread.php?do=newthread&f=283"><img src="images/misc/adbox-left.g…

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

  • Error Line 2048, Column 76: reference to entity "f" for which no system identifier could be generated
    …at.com/vb/newthread.php?do=newthread&f=283"><img src="images/misc/adbox-left.g…

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

  • Info Line 2048, Column 74: entity was defined here
    …-sat.com/vb/newthread.php?do=newthread&f=283"><img src="images/misc/adbox-left…
  • Error Line 2048, Column 130: required attribute "alt" not specified
    …ewthread&f=283"><img src="images/misc/adbox-left.gif" border="0"></a></td></tr>

    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 2048, Column 134: end tag for "img" omitted, but OMITTAG NO was specified
    …ewthread&f=283"><img src="images/misc/adbox-left.gif" border="0"></a></td></tr>

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

  • Info Line 2048, Column 82: start tag was here
    …/vb/newthread.php?do=newthread&f=283"><img src="images/misc/adbox-left.gif" bo…
  • Error Line 2055, Column 126: value of attribute "align" cannot be "center"; must be one of "top", "middle", "bottom", "left", "right"
    …if" alt="إحصائيات منتديات تونيزيـا سات" border="0" align="center" /></div><br/>

    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 2081, Column 152: end tag for "br" omitted, but OMITTAG NO was specified
    …true',blog : 'false',group : 'false',vm : 'false',sig : 'false'});</script><br>

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

  • Info Line 2081, Column 148: start tag was here
    …true',blog : 'false',group : 'false',vm : 'false',sig : 'false'});</script><br>
  • Error Line 2102, Column 94: document type does not allow element "table" here
    …cing="0" align="right" class="banner-c"><tr align="center"><td class="newfoot">

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 2114, Column 18: there is no attribute "ONCHANGE"
    <SELECT ONCHANGE="location = this.options[this.selectedIndex].value;">

    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 2114, Column 70: element "SELECT" undefined
    <SELECT ONCHANGE="location = this.options[this.selectedIndex].value;">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2116, Column 15: there is no attribute "VALUE"
    <OPTION VALUE="http://www.tunisia-sat.com/vb/index.php">Original Language

    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 2116, Column 56: element "OPTION" undefined
    <OPTION VALUE="http://www.tunisia-sat.com/vb/index.php">Original Language

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 2117, Column 79: cannot generate system identifier for general entity "hl"
    …nslate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to Eng…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2117, Column 79: general entity "hl" not defined and no default entity
    …nslate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to Eng…

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

  • Warning Line 2117, Column 81: reference not terminated by REFC delimiter
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to Engli…

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

  • Warning Line 2117, Column 81: reference to external entity in attribute value
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to Engli…

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

  • Error Line 2117, Column 81: reference to entity "hl" for which no system identifier could be generated
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to Engli…

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

  • Info Line 2117, Column 78: entity was defined here
    …anslate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to En…
  • Warning Line 2117, Column 85: cannot generate system identifier for general entity "ie"
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2117, Column 85: general entity "ie" not defined and no default entity
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Warning Line 2117, Column 87: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Warning Line 2117, Column 87: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Error Line 2117, Column 87: reference to entity "ie" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Info Line 2117, Column 84: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Warning Line 2117, Column 93: cannot generate system identifier for general entity "sl"
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2117, Column 93: general entity "sl" not defined and no default entity
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Warning Line 2117, Column 95: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Warning Line 2117, Column 95: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Error Line 2117, Column 95: reference to entity "sl" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Info Line 2117, Column 92: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Warning Line 2117, Column 99: cannot generate system identifier for general entity "tl"
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2117, Column 99: general entity "tl" not defined and no default entity
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Warning Line 2117, Column 101: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Warning Line 2117, Column 101: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Error Line 2117, Column 101: reference to entity "tl" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

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

  • Info Line 2117, Column 98: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Error Line 2117, Column 105: element "OPTION" undefined
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 2118, Column 81: reference not terminated by REFC delimiter
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to Frenc…

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

  • Warning Line 2118, Column 81: reference to external entity in attribute value
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to Frenc…

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

  • Error Line 2118, Column 81: reference to entity "hl" for which no system identifier could be generated
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to Frenc…

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

  • Info Line 2117, Column 78: entity was defined here
    …anslate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to En…
  • Warning Line 2118, Column 87: reference not terminated by REFC delimiter
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to French

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

  • Warning Line 2118, Column 87: reference to external entity in attribute value
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to French

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

  • Error Line 2118, Column 87: reference to entity "ie" for which no system identifier could be generated
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to French

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

  • Info Line 2117, Column 84: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Warning Line 2118, Column 95: reference not terminated by REFC delimiter
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to French

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

  • Warning Line 2118, Column 95: reference to external entity in attribute value
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to French

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

  • Error Line 2118, Column 95: reference to entity "sl" for which no system identifier could be generated
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to French

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

  • Info Line 2117, Column 92: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Warning Line 2118, Column 101: reference not terminated by REFC delimiter
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to French

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

  • Warning Line 2118, Column 101: reference to external entity in attribute value
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to French

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

  • Error Line 2118, Column 101: reference to entity "tl" for which no system identifier could be generated
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to French

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

  • Info Line 2117, Column 98: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Error Line 2118, Column 105: element "OPTION" undefined
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=fr">Arabic to French

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 2119, Column 81: reference not terminated by REFC delimiter
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arab…

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

  • Warning Line 2119, Column 81: reference to external entity in attribute value
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arab…

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

  • Error Line 2119, Column 81: reference to entity "hl" for which no system identifier could be generated
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arab…

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

  • Info Line 2117, Column 78: entity was defined here
    …anslate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to En…
  • Warning Line 2119, Column 87: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arabic

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

  • Warning Line 2119, Column 87: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arabic

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

  • Error Line 2119, Column 87: reference to entity "ie" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arabic

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

  • Info Line 2117, Column 84: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Warning Line 2119, Column 95: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arabic

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

  • Warning Line 2119, Column 95: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arabic

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

  • Error Line 2119, Column 95: reference to entity "sl" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arabic

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

  • Info Line 2117, Column 92: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Warning Line 2119, Column 101: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arabic

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

  • Warning Line 2119, Column 101: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arabic

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

  • Error Line 2119, Column 101: reference to entity "tl" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arabic

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

  • Info Line 2117, Column 98: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Error Line 2119, Column 105: element "OPTION" undefined
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=ar">English to Arabic

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 2120, Column 81: reference not terminated by REFC delimiter
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to Fren…

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

  • Warning Line 2120, Column 81: reference to external entity in attribute value
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to Fren…

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

  • Error Line 2120, Column 81: reference to entity "hl" for which no system identifier could be generated
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to Fren…

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

  • Info Line 2117, Column 78: entity was defined here
    …anslate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to En…
  • Warning Line 2120, Column 87: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to French

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

  • Warning Line 2120, Column 87: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to French

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

  • Error Line 2120, Column 87: reference to entity "ie" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to French

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

  • Info Line 2117, Column 84: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Warning Line 2120, Column 95: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to French

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

  • Warning Line 2120, Column 95: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to French

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

  • Error Line 2120, Column 95: reference to entity "sl" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to French

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

  • Info Line 2117, Column 92: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Warning Line 2120, Column 101: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to French

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

  • Warning Line 2120, Column 101: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to French

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

  • Error Line 2120, Column 101: reference to entity "tl" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to French

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

  • Info Line 2117, Column 98: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Error Line 2120, Column 105: element "OPTION" undefined
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=en&tl=fr">English to French

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 2121, Column 81: reference not terminated by REFC delimiter
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to Engli…

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

  • Warning Line 2121, Column 81: reference to external entity in attribute value
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to Engli…

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

  • Error Line 2121, Column 81: reference to entity "hl" for which no system identifier could be generated
    …late?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to Engli…

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

  • Info Line 2117, Column 78: entity was defined here
    …anslate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to En…
  • Warning Line 2121, Column 87: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to English

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

  • Warning Line 2121, Column 87: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to English

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

  • Error Line 2121, Column 87: reference to entity "ie" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to English

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

  • Info Line 2117, Column 84: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Warning Line 2121, Column 95: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to English

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

  • Warning Line 2121, Column 95: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to English

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

  • Error Line 2121, Column 95: reference to entity "sl" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to English

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

  • Info Line 2117, Column 92: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Warning Line 2121, Column 101: reference not terminated by REFC delimiter
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to English

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

  • Warning Line 2121, Column 101: reference to external entity in attribute value
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to English

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

  • Error Line 2121, Column 101: reference to entity "tl" for which no system identifier could be generated
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to English

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

  • Info Line 2117, Column 98: entity was defined here
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=ar&tl=en">Arabic to English
  • Error Line 2121, Column 105: element "OPTION" undefined
    …ate?u=http%3A%2F%2Ftunisia-sat.com&hl=en&ie=UTF8&sl=fr&tl=en">French to English

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2122, Column 11: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </optgroup>

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

  • Info Line 2121, Column 1: start tag was here
    <OPTION VALUE="http://www.google.com/translate?u=http%3A%2F%2Ftunisia-sat.com&h…
  • Error Line 2122, Column 11: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </optgroup>

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

  • Info Line 2120, Column 1: start tag was here
    <OPTION VALUE="http://www.google.com/translate?u=http%3A%2F%2Ftunisia-sat.com&h…
  • Error Line 2122, Column 11: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </optgroup>

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

  • Info Line 2119, Column 1: start tag was here
    <OPTION VALUE="http://www.google.com/translate?u=http%3A%2F%2Ftunisia-sat.com&h…
  • Error Line 2122, Column 11: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </optgroup>

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

  • Info Line 2118, Column 1: start tag was here
    <OPTION VALUE="http://www.google.com/translate?u=http%3A%2F%2Ftunisia-sat.com&h…
  • Error Line 2122, Column 11: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </optgroup>

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

  • Info Line 2117, Column 1: start tag was here
    <OPTION VALUE="http://www.google.com/translate?u=http%3A%2F%2Ftunisia-sat.com&h…
  • Error Line 2122, Column 11: end tag for "OPTION" omitted, but OMITTAG NO was specified
    </optgroup>

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

  • Info Line 2116, Column 1: start tag was here
    <OPTION VALUE="http://www.tunisia-sat.com/vb/index.php">Original Language
  • Error Line 2122, Column 11: end tag for "optgroup" which is not finished
    </optgroup>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 2134, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    …howrules"><img src="images/misc/icons/tos.png" border="0" alt="TOS"></a> &nbsp;

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

  • Info Line 2134, Column 33: start tag was here
    <a href="misc.php?do=showrules"><img src="images/misc/icons/tos.png" border="0"…
  • Error Line 2136, Column 167: end tag for "img" omitted, but OMITTAG NO was specified
    …"><img src="images/misc/icons/contact_us.png" border="0" alt="الإتصال بنا"></a>

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

  • Info Line 2136, Column 91: start tag was here
    …f4762eb" rel="nofollow" accesskey="9"><img src="images/misc/icons/contact_us.p…
  • Error Line 2139, Column 117: end tag for "img" omitted, but OMITTAG NO was specified
    …="images/misc/icons/ts.png" border="0" alt="*منتديات تونيزيـا سات*"></a> &nbsp;

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

  • Info Line 2139, Column 38: start tag was here
    <a href="http://www.tunisia-sat.com"><img src="images/misc/icons/ts.png" border…
  • Error Line 2141, Column 98: end tag for "img" omitted, but OMITTAG NO was specified
    …"><img src="images/misc/icons/archive.png" border="0" alt="الأرشيف"></a> &nbsp;

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

  • Info Line 2141, Column 29: start tag was here
    <a href="archive/index.php"><img src="images/misc/icons/archive.png" border="0"…
  • Error Line 2147, Column 128: end tag for "img" omitted, but OMITTAG NO was specified
    …return false;"><img src="images/misc/icons/up.png" border="0" alt="الأعلى"></a>

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

  • Info Line 2147, Column 65: start tag was here
    …="self.scrollTo(0, 0); return false;"><img src="images/misc/icons/up.png" bord…
  • Error Line 2155, Column 19: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div align="right">

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

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

  • Error Line 2170, Column 14: end tag for "div" omitted, but OMITTAG NO was specified
    	</div></font>

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

  • Info Line 2155, Column 1: start tag was here
    <div align="right">
  • Error Line 2173, 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.

  • Warning Line 2194, Column 1: character "<" is the first character of a delimiter but occurred as data
    <! -- bottom bar -->

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 2198, Column 7: end tag for element "body" which is not open
    </body>

    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 2199, Column 8: character data is not allowed here
    </html>Facebook Official Page onmouseover=b

    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.

Visitor Analysis

Daily Visitor
  • 28.000 visits
Daily Visitor

In Page Analysis