Ethiopian news: aigaforum.com is reliable source for Ethiopian related News. You will find daily Ethiopian News, topical discussion forum Blog ...

aigaforum.com
  • Domain Name
    aigaforum.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #57199
  • Page Size
    56.1 KB
  • Ip Address
    67.195.61.65
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 1, H5: 0, H6: 0
  • Images
    61 GIF, 12 JPG, 2 PNG

Website Meta Analysis

  • Title
    Aiga Forum, an Ethiopian forum for news and views promoting Ethiopia's Unity in Diversity!
  • Meta Keyword
    ethiopia, Ethiopia, ethiopia news, news ethiopia, aiga, aigaforum, aiga forum, woyane,news, ethio, zena, ethiopian culture, ethiopian people, Ethiopian art, tigrai, tigray, coffee, Mekelle, Adwa, Axum, Shire, Wukro, Kilte Awlaelo, Adigrat, Agame,Enderta, Raya, Michew, ethiopian music,wolqaite, ethiomusic, ethiopian music videos, zefen, newethiopia, federal ethiopia, addis ababa, tizita, amharic, tigrigna, oromigna, gurgigna, eritrea news, tigrai music, Abyssinia, afar rift valley, Axumite kingdom, King Yohaness, General Alula, Ras Alula,Atse-Yohaness, battle of Adwa, Struggle, Solommon Dynasty, Ras Alula, orginal ark, blue nile,habesha, lalibela, geez, ge'ez, amhara, red sea, adulis, yohannes, circus tigray, TPLF, EPRDF, eprdf-sf
  • Meta Description
    Ethiopian news: aigaforum.com is reliable source for Ethiopian related News. You will find daily Ethiopian News, topical discussion forum Blog

Technical Analysis

  • Webserver
    YTS/1.20.28
  • Ip Address
    67.195.61.65
  • Domain Age
    9 Years, 0 Months, 28 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 21 Aug 2013 08:48:28 GMT
  • p3p: policyref="http://info.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE LOC GOV"
  • content-type: text/html
  • age: 0
  • connection: keep-alive
  • server: YTS/1.20.28
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for aigaforum.com

DNS Analysis


DNS servers
yns1.yahoo.com [67.195.1.92]
yns2.yahoo.com [98.139.247.192]


DNS Records

Answer records
aigaforum.com TXT i=263&m=geo-g5-mx2-p6 120s
aigaforum.com A 67.195.61.65 120s
aigaforum.com MX
preference: 30
exchange: mx5.biz.mail.yahoo.com
120s
aigaforum.com MX
preference: 20
exchange: mx1.biz.mail.yahoo.com
120s
aigaforum.com NS  yns2.yahoo.com 86400s
aigaforum.com NS  yns1.yahoo.com 86400s
aigaforum.com SOA
server: hidden-master.yahoo.com
email: geo-support@yahoo-inc.com
serial: 2012101501
refresh: 10800
retry: 3600
expire: 7084000
minimum ttl: 28800
120s

Authority records

Additional records

IP 67.195.61.65 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Sunnyvale
  • Continent Code
    94089
  • Latitude
    408
  • Longitude
    807
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 67.195.61.65"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=67.195.61.65?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 67.195.0.0 - 67.195.255.255
    CIDR: 67.195.0.0/16
    OriginAS:
    NetName: A-YAHOO-US8
    NetHandle: NET-67-195-0-0-1
    Parent: NET-67-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2007-09-13
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-67-195-0-0-1

    OrgName: Yahoo! Inc.
    OrgId: YHOO
    Address: 701 First Ave
    City: Sunnyvale
    StateProv: CA
    PostalCode: 94089
    Country: US
    RegDate: 2000-10-23
    Updated: 2009-05-18
    Ref: http://whois.arin.net/rest/org/YHOO

    OrgAbuseHandle: NETWO857-ARIN
    OrgAbuseName: Network Abuse
    OrgAbusePhone: +1-408-349-3300
    OrgAbuseEmail:
    OrgAbuseRef: http://whois.arin.net/rest/poc/NETWO857-ARIN

    OrgTechHandle: NA258-ARIN
    OrgTechName: Netblock Admin
    OrgTechPhone: +1-408-349-3300
    OrgTechEmail:
    OrgTechRef: http://whois.arin.net/rest/poc/NA258-ARIN

    RAbuseHandle: NETWO857-ARIN
    RAbuseName: Network Abuse
    RAbusePhone: +1-408-349-3300
    RAbuseEmail:
    RAbuseRef: http://whois.arin.net/rest/poc/NETWO857-ARIN

    RTechHandle: NA258-ARIN
    RTechName: Netblock Admin
    RTechPhone: +1-408-349-3300
    RTechEmail:
    RTechRef: http://whois.arin.net/rest/poc/NA258-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

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

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

  • Warning Line 5, Column 40: NET-enabling start-tag requires SHORTTAG YES
    <base href="http://www.aigaforum.com/" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 5, Column 41: character data is not allowed here
    <base href="http://www.aigaforum.com/" />

    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.
  • Warning Line 8, Column 67: NET-enabling start-tag requires SHORTTAG YES
     <meta name="alexaVerifyID" content="6oI_cx-apyBb6lwKzKOgnnauQGc" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 10, Column 776: NET-enabling start-tag requires SHORTTAG YES
    …'ez, amhara, red sea, adulis, yohannes, circus tigray, TPLF, EPRDF, eprdf-sf"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 10, Column 776: document type does not allow element "META" here
    …'ez, amhara, red sea, adulis, yohannes, circus tigray, TPLF, EPRDF, eprdf-sf"/>

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

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

  • Warning Line 12, Column 182: NET-enabling start-tag requires SHORTTAG YES
    …ed News. You will find daily Ethiopian News, topical discussion forum Blog " />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 12, Column 182: document type does not allow element "META" here
    …ed News. You will find daily Ethiopian News, topical discussion forum Blog " />

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 15, Column 93: document type does not allow element "LINK" here
    …tp://aigaforum.com/images/viewpointStyle.css" rel="stylesheet" type="text/css">

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

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

  • Error Line 25, Column 23: document type does not allow element "STYLE" here
    <style type="text/css"> 

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

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

  • Warning Line 32, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <meta name="verify-v1" content="12x7ytpyihwkzB/xbmz3gpj0HNXZfs0ZKcKHfdrX2Rs=" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 32, Column 79: document type does not allow element "META" here
    <meta name="verify-v1" content="12x7ytpyihwkzB/xbmz3gpj0HNXZfs0ZKcKHfdrX2Rs=" />

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

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

  • Warning Line 33, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="VhuqGIkELZq2Yi0oDQ9LCpF9FpdQYgGurKYBoCN-nzI" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 33, Column 93: document type does not allow element "META" here
    …gle-site-verification" content="VhuqGIkELZq2Yi0oDQ9LCpF9FpdQYgGurKYBoCN-nzI" />

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

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

  • Warning Line 34, Column 75: NET-enabling start-tag requires SHORTTAG YES
    <link rel="SHORTCUT ICON" href="http://aigaforum.com/images/aigalogo.bmp" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 34, Column 75: document type does not allow element "LINK" here
    <link rel="SHORTCUT ICON" href="http://aigaforum.com/images/aigalogo.bmp" />

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 35, Column 7: end tag for element "HEAD" which is not open
    </head>

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

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

  • Error Line 39, Column 88: required attribute "TYPE" not specified
    …://us.js2.yimg.com/us.js.yimg.com/lib/smb/js/hosting/cp/js_source/whv2_001.js">

    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 41, Column 30: required attribute "TYPE" not specified
    <script language="javascript">geovisit();</script>

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

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

  • Error Line 45, Column 6: document type does not allow element "BODY" here
    <body>

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

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

  • Warning Line 51, Column 349: NET-enabling start-tag requires SHORTTAG YES
    …=Z00lf1asZt0005" style="display:none" height="1" width="1" alt="" /></noscript>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 53, Column 72: there is no attribute "STYLEE"
    … border="1" cellspacing="0" cellpadding="0" stylee="border:solid 1px #3366CC;">

    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.

  • Warning Line 100, Column 203: NET-enabling start-tag requires SHORTTAG YES
    …ash_player.gif" alt="Get Adobe Flash player" width="100" height="33" /></a></p>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 114, Column 10: NET-enabling start-tag requires SHORTTAG YES
          <br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 120, Column 23: document type does not allow element "STYLE" here
    <style type="text/css">

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

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

  • Warning Line 127, Column 88: NET-enabling start-tag requires SHORTTAG YES
    …nput type="hidden" name="cx" value="partner-pub-2230485263630942:8365049890" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 128, Column 58: NET-enabling start-tag requires SHORTTAG YES
            <input type="hidden" name="cof" value="FORID:10" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 129, Column 54: NET-enabling start-tag requires SHORTTAG YES
            <input type="hidden" name="ie" value="UTF-8" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 130, Column 47: NET-enabling start-tag requires SHORTTAG YES
            <input type="text" name="q" size="30" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 131, Column 55: NET-enabling start-tag requires SHORTTAG YES
            <input type="submit" name="sa" value="Search" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 136, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …w.google.com/images/poweredby_transparent/poweredby_FFFFFF.gif" alt="Google" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

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

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

  • Info Line 146, Column 1: start tag was here
    <div align=center>
  • Error Line 179, Column 20: document type does not allow element "TD" here
    			<td valign="top"><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 183, Column 55: document type does not allow element "DIV" here; missing one of "TH", "TD" start-tag
    <div align="right" style="padding-top:0;margin-top:0;"> 

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

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

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

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

  • Info Line 180, Column 5: start tag was here
    				<table class="aigamenu" cellspacing="0" cellpadding="0" border="0">
  • Error Line 184, Column 13: end tag for "DIV" omitted, but its declaration does not permit this
    		</div></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 179, Column 21: start tag was here
    			<td valign="top"><div align=center>
  • Error Line 186, Column 29: document type does not allow element "TD" here
    <td width="820" height="250"><span class="footer">

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 188, Column 18: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <div align=center>

    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 190, Column 110: required attribute "ALT" not specified
    …o.uk/media/images/66143000/jpg/_66143770_66141598.jpg" width="200" align=right>

    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 191, Column 160: end tag for "SPAN" omitted, but its declaration does not permit this
    …:blue'>Ethiopian church appoints Abune Mathias as patriarch.</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 191, Column 62: start tag was here
    …bbc.co.uk/news/world-africa-21627611"><span style='font-size:12.0pt;color:blue…
  • Error Line 191, Column 171: end tag for "DIV" omitted, but its declaration does not permit this
    …:blue'>Ethiopian church appoints Abune Mathias as patriarch.</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 188, Column 1: start tag was here
    <div align=center>
  • Error Line 201, Column 6: end tag for "TABLE" omitted, but its declaration does not permit this
    </div><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 56, Column 3: start tag was here
    		<table width="100%" border="0" cellspacing="0" cellpadding="0">
  • Error Line 201, Column 6: end tag for "TABLE" omitted, but its declaration does not permit this
    </div><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 53, Column 2: start tag was here
    	<table width="100%" border="1" cellspacing="0" cellpadding="0" stylee="border:…
  • Error Line 217, Column 5: end tag for element "TD" which is not open
    </td>

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

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

  • Error Line 219, Column 28: document type does not allow element "TD" here
    <td width="10" height="250"> <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 225, Column 7: end tag for element "SPAN" which is not open
    </span>

    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 228, Column 7: end tag for element "SPAN" which is not open
    </span>

    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 229, Column 5: end tag for element "TD" which is not open
    </td>

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

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

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

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

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

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

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

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

  • Error Line 234, Column 5: end tag for element "TD" which is not open
    </td></tr></table>

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

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

  • Error Line 234, Column 10: end tag for element "TR" which is not open
    </td></tr></table>

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

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

  • Error Line 234, Column 18: end tag for element "TABLE" which is not open
    </td></tr></table>

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

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

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

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

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

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

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

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

  • Error Line 247, Column 4: document type does not allow element "TR" here
    <tr><td style="background-color:ivory;padding:0;margin:0;"></div>

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 247, Column 65: end tag for element "DIV" which is not open
    <tr><td style="background-color:ivory;padding:0;margin:0;"></div>

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

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

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

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

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

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

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

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

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

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

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

  • Error Line 253, Column 5: document type does not allow element "TR" here
    	<tr><td style="background-color:ivory;padding:0;margin:0;">

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 262, Column 30: there is no attribute "HEIGHT"
    <table   width="100%" height="100%"  border="0" cellpadding="0" cellspacing="0">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 293, Column 47: required attribute "ALT" not specified
    …="http://aigaforum.com/Audio_logo.gif">&nbsp <a href="http://www1.voanews.com/…

    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 293, Column 186: required attribute "ALT" not specified
    …="http://aigaforum.com/Audio_logo.gif">&nbsp<a href="http://www.radiofanabroad…

    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 294, Column 53: required attribute "ALT" not specified
    …="http://aigaforum.com/Audio_logo.gif">&nbsp <a href=" http://www.dmtsiweyane.…

    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 301, Column 7: end tag for "B" omitted, but its declaration does not permit this
    </span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 275, Column 2: start tag was here
    	<b>&nbsp <a href="http://www.mfa.gov.et/"><font color=blue> MFA</font></a>| 
  • Error Line 318, Column 6: document type does not allow element "TR" here
    		<tr><td valign="top">

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 336, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <span class="footer"><div align=center>

    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 337, Column 72: an attribute specification must start with a name or name token
    <img src="http://www.aigaforum.com/images/Tsinat2-Poster.jpg" width=220"><br>

    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 339, Column 172: end tag for "SPAN" omitted, but its declaration does not permit this
    …4664;&#4725; &#4637;&#4661; &#4771;&#4621;&#4771;&#4634;&#4757;></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 338, Column 4: start tag was here
    <b><span style='font-size:12.0pt;color:blue'>
  • Error Line 339, Column 179: end tag for "DIV" omitted, but its declaration does not permit this
    …4664;&#4725; &#4637;&#4661; &#4771;&#4621;&#4771;&#4634;&#4757;></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 336, Column 22: start tag was here
    <span class="footer"><div align=center>
  • Error Line 341, Column 105: end tag for "SPAN" omitted, but its declaration does not permit this
    …dex.php"><span style='font-size:11.0pt;color:red'>click here!</a></b><span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 341, Column 50: start tag was here
    …"http://aigaforum.com/geez-index.php"><span style='font-size:11.0pt;color:red'…
  • Error Line 346, Column 70: end tag for element "DIV" which is not open
    <br><img src="images/hr_main.gif" alt="" width="220" height="8"></div>

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

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

  • Error Line 349, Column 18: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <div align=center>

    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 368, Column 18: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <div align=center>

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

  • Warning Line 370, Column 112: cannot generate system identifier for general entity "fs"
    …utube.com/p/06F004455CD09946?hl=en_US&fs=1"></param><param name="allowFullScre…

    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 370, Column 112: general entity "fs" not defined and no default entity
    …utube.com/p/06F004455CD09946?hl=en_US&fs=1"></param><param name="allowFullScre…

    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.

  • Error Line 370, Column 114: reference to entity "fs" for which no system identifier could be generated
    …ube.com/p/06F004455CD09946?hl=en_US&fs=1"></param><param name="allowFullScreen…

    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 370, Column 111: entity was defined here
    …outube.com/p/06F004455CD09946?hl=en_US&fs=1"></param><param name="allowFullScr…
  • Error Line 370, Column 125: end tag for element "PARAM" which is not open
    …6F004455CD09946?hl=en_US&fs=1"></param><param name="allowFullScreen" value="tr…

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

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

  • Error Line 370, Column 176: end tag for element "PARAM" which is not open
    …"allowFullScreen" value="true"></param><param name="allowscriptaccess" value="…

    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 370, Column 231: end tag for element "PARAM" which is not open
    …owscriptaccess" value="always"></param><embed src="http://www.youtube.com/p/06…

    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 370, Column 243: there is no attribute "SRC"
    …ss" value="always"></param><embed src="http://www.youtube.com/p/06F004455CD099…

    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 370, Column 297: reference to entity "fs" for which no system identifier could be generated
    …ube.com/p/06F004455CD09946?hl=en_US&fs=1" type="application/x-shockwave-flash"…

    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 370, Column 111: entity was defined here
    …outube.com/p/06F004455CD09946?hl=en_US&fs=1"></param><param name="allowFullScr…
  • Error Line 370, Column 306: there is no attribute "TYPE"
    …/06F004455CD09946?hl=en_US&fs=1" type="application/x-shockwave-flash" width="2…

    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 370, Column 344: there is no attribute "WIDTH"
    …"application/x-shockwave-flash" width="220" height="200" allowscriptaccess="al…

    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 370, Column 357: there is no attribute "HEIGHT"
    …x-shockwave-flash" width="220" height="200" allowscriptaccess="always" allowfu…

    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 370, Column 381: there is no attribute "ALLOWSCRIPTACCESS"
    …="220" height="200" allowscriptaccess="always" allowfullscreen="true"></embed>…

    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 370, Column 406: there is no attribute "ALLOWFULLSCREEN"
    …t="200" allowscriptaccess="always" allowfullscreen="true"></embed></object><br>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 370, Column 412: element "EMBED" undefined
    …t="200" allowscriptaccess="always" allowfullscreen="true"></embed></object><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 372, Column 66: end tag for "SPAN" omitted, but its declaration does not permit this
    <span style='font-size:11.0pt;color:blue'>For more click here!</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 372, Column 1: start tag was here
    <span style='font-size:11.0pt;color:blue'>For more click here!</a></b></span>
  • Error Line 372, Column 77: end tag for "DIV" omitted, but its declaration does not permit this
    <span style='font-size:11.0pt;color:blue'>For more click here!</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 368, Column 1: start tag was here
    <div align=center>
  • Error Line 377, Column 18: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <div align=center>

    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 380, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 382, Column 51: end tag for "SPAN" omitted, but its declaration does not permit this
    <span style='font-size:11.0pt;color:red'>Hateta</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 382, Column 1: start tag was here
    <span style='font-size:11.0pt;color:red'>Hateta</a></b></span>
  • Error Line 382, Column 62: end tag for "DIV" omitted, but its declaration does not permit this
    <span style='font-size:11.0pt;color:red'>Hateta</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 377, Column 1: start tag was here
    <div align=center>
  • Error Line 384, Column 70: end tag for element "DIV" which is not open
    <br><img src="images/hr_main.gif" alt="" width="200" height="8"></div><br>

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

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

  • Error Line 392, Column 71: end tag for "SPAN" omitted, but its declaration does not permit this
    …ults from the recently held leases bid- Mekelle, Tigrai 02/21/13</b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 391, Column 4: start tag was here
    <b><span style='font-size:11.0pt;color:blue'>
  • Error Line 392, Column 78: end tag for element "SPAN" which is not open
    …ults from the recently held leases bid- Mekelle, Tigrai 02/21/13</b></span><br>

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

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

  • Error Line 394, Column 130: end tag for element "B" which is not open
    …2; &#4904;&#4648;&#4723; &#4618;&#4829; &#4673;&#4933;&#4650; 40</b></span><br>

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

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

  • Error Line 395, Column 103: end tag for "SPAN" omitted, but its declaration does not permit this
    …-index.php"><span style='font-size:11.0pt;color:red'>for more</a></b><span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 395, Column 51: start tag was here
    …"http://aigaforum.com/geez-index.php"><span style='font-size:11.0pt;color:red'…
  • Error Line 398, Column 70: end tag for "SPAN" omitted, but its declaration does not permit this
    <br><img src="images/hr_main.gif" alt="" width="200" height="8"></div><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 395, Column 108: start tag was here
    …-index.php"><span style='font-size:11.0pt;color:red'>for more</a></b><span><br>
  • Error Line 403, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 405, Column 54: end tag for "SPAN" omitted, but its declaration does not permit this
    <span style='font-size:11.0pt;color:red'>Interview</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 405, Column 1: start tag was here
    <span style='font-size:11.0pt;color:red'>Interview</a></b></span>
  • Error Line 405, Column 65: end tag for element "SPAN" which is not open
    <span style='font-size:11.0pt;color:red'>Interview</a></b></span>

    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 411, Column 119: end tag for "SPAN" omitted, but its declaration does not permit this
    …ok.php"><span style='font-size:11.0pt;color:blue'> Tenfashe!</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 411, Column 64: start tag was here
    …rum.com/events/tenfashe-new-book.php"><span style='font-size:11.0pt;color:blue…
  • Error Line 411, Column 130: end tag for element "SPAN" which is not open
    …ok.php"><span style='font-size:11.0pt;color:blue'> Tenfashe!</a></b></span><br>

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

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

  • Error Line 412, Column 96: required attribute "ALT" not specified
    …aigaforum.com/events/tenfashe1-new-book-zeryihun.jpg" width="220" height="170">

    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 415, Column 70: end tag for element "DIV" which is not open
    <br><img src="images/hr_main.gif" alt="" width="200" height="8"></div><br>

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

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

  • Error Line 429, Column 7: end tag for element "SPAN" which is not open
    </span></td>

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

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

  • Error Line 435, Column 21: character "!" not allowed in attribute specification list
    			<td valign="top" !width="50%">
  • Error Line 451, Column 38: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
     <span class="footer"><div align=left><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 454, Column 133: end tag for "SPAN" omitted, but its declaration does not permit this
    …pt;color:blue'>What Else Can I Say?</a></b></span><br><span style='font-size:1…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 454, Column 68: start tag was here
    …com/articles/what-else-can-i-say.php"><span style='font-size:11.0pt;color:blue…
  • Error Line 454, Column 144: end tag for "DIV" omitted, but its declaration does not permit this
    …ue'>What Else Can I Say?</a></b></span><br><span style='font-size:10.0pt;color…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 451, Column 23: start tag was here
     <span class="footer"><div align=left><br>
  • Error Line 472, Column 178: end tag for "SPAN" omitted, but its declaration does not permit this
    …ost Of Two Key Continental Events!.</a></b></span><br><span style='font-size:1…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 472, Column 77: start tag was here
    …rticles/Ethiopia-the-pround-host.pdf"><span style='font-size:11.0pt;color:blue…
  • Error Line 472, Column 189: end tag for element "SPAN" which is not open
    …Key Continental Events!.</a></b></span><br><span style='font-size:10.0pt;color…

    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 474, Column 175: end tag for "SPAN" omitted, but its declaration does not permit this
    …1.0pt;color:blue'>IGAD ask for a peaceful Election in Kenya.</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 474, Column 88: start tag was here
    …-dr-tedors-keneya-election-visit.pdf"><span style='font-size:11.0pt;color:blue…
  • Error Line 474, Column 186: end tag for element "SPAN" which is not open
    …1.0pt;color:blue'>IGAD ask for a peaceful Election in Kenya.</a></b></span><br>

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

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

  • Error Line 478, Column 155: end tag for "SPAN" omitted, but its declaration does not permit this
    …s Ranked by Military Strength -2013</a></b></span><br><span style='font-size:1…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 478, Column 67: start tag was here
    …lfirepower.com/countries-listing.asp"><span style='font-size:11.0pt;color:blue…
  • Error Line 478, Column 166: end tag for element "SPAN" which is not open
    … Military Strength -2013</a></b></span><br><span style='font-size:10.0pt;color…

    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 483, Column 53: cannot generate system identifier for general entity "a"
    <a href="http://clk.tradedoubler.com/click?p=203491&a=2080536&g=20723196">

    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 483, Column 53: general entity "a" not defined and no default entity
    <a href="http://clk.tradedoubler.com/click?p=203491&a=2080536&g=20723196">

    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.

  • Error Line 483, Column 54: reference to entity "a" for which no system identifier could be generated
    <a href="http://clk.tradedoubler.com/click?p=203491&a=2080536&g=20723196">

    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 483, Column 52: entity was defined here
    <a href="http://clk.tradedoubler.com/click?p=203491&a=2080536&g=20723196">
  • Warning Line 483, Column 63: cannot generate system identifier for general entity "g"
    <a href="http://clk.tradedoubler.com/click?p=203491&a=2080536&g=20723196">

    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 483, Column 63: general entity "g" not defined and no default entity
    <a href="http://clk.tradedoubler.com/click?p=203491&a=2080536&g=20723196">

    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.

  • Error Line 483, Column 64: reference to entity "g" for which no system identifier could be generated
    <a href="http://clk.tradedoubler.com/click?p=203491&a=2080536&g=20723196">

    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 483, Column 62: entity was defined here
    <a href="http://clk.tradedoubler.com/click?p=203491&a=2080536&g=20723196">
  • Error Line 484, Column 79: required attribute "ALT" not specified
    … src="http://aigaforum.com/events/Ethiopia-480x60-100-EN-USD.gif" border=0></a>

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

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

  • Error Line 489, Column 107: end tag for "SPAN" omitted, but its declaration does not permit this
    … - &#4768;&#4941;&#4650;&#4779;&#4810;&#4727; &#4638;&#4852;&#4621; </b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 488, Column 4: start tag was here
    <b><span style='font-size:11.0pt;color:blue'>
  • Error Line 489, Column 114: end tag for element "SPAN" which is not open
    … - &#4768;&#4941;&#4650;&#4779;&#4810;&#4727; &#4638;&#4852;&#4621; </b></span>

    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 490, Column 106: end tag for "SPAN" omitted, but its declaration does not permit this
    …-index.php"><span style='font-size:11.0pt;color:red'>for more</a></b><span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 490, Column 54: start tag was here
    …"http://aigaforum.com/geez-index.php"><span style='font-size:11.0pt;color:red'…
  • Error Line 493, Column 148: end tag for "SPAN" omitted, but its declaration does not permit this
    …#4725; &#4720;&#4632;&#4650;&#4689;</b></span>....<b><a href="http://aigaforum…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 492, Column 4: start tag was here
    <b><span style='font-size:12.0pt;color:blue'>
  • Error Line 493, Column 261: end tag for "SPAN" omitted, but its declaration does not permit this
    …-index.php"><span style='font-size:11.0pt;color:red'>for more</a></b><span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 493, Column 209: start tag was here
    …"http://aigaforum.com/geez-index.php"><span style='font-size:11.0pt;color:red'…
  • Error Line 496, Column 69: end tag for "SPAN" omitted, but its declaration does not permit this
    …ng’ international climate efforts  </a></b></span><br><span style='font-size:1…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 495, Column 96: start tag was here
    …esting-international-climate-efforts"><span style='font-size:11.0pt;color:blue…
  • Error Line 501, Column 49: end tag for "SPAN" omitted, but its declaration does not permit this
    … (LON: TLW) Discovers Ethiopian Oil</a></b></span><br><span style='font-size:1…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 500, Column 103: start tag was here
    …lon-tlw-discovers-ethiopian-oil/3126"><span style='font-size:11.0pt;color:blue…
  • Error Line 501, Column 60: end tag for element "SPAN" which is not open
    … Discovers Ethiopian Oil</a></b></span><br><span style='font-size:10.0pt;color…

    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 506, Column 137: end tag for "SPAN" omitted, but its declaration does not permit this
    …4773;&#4659;&#4721;&#4661; &#4768;&#4650;&#4941; &#4752;&#4813;"</b></span>....
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 505, Column 4: start tag was here
    <b><span style='font-size:11.0pt;color:blue'>
  • Error Line 506, Column 144: end tag for element "SPAN" which is not open
    …4773;&#4659;&#4721;&#4661; &#4768;&#4650;&#4941; &#4752;&#4813;"</b></span>....

    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 507, Column 102: end tag for "SPAN" omitted, but its declaration does not permit this
    …-index.php"><span style='font-size:11.0pt;color:red'>for more</a></b><span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 507, Column 50: start tag was here
    …"http://aigaforum.com/geez-index.php"><span style='font-size:11.0pt;color:red'…
  • Error Line 513, Column 34: end tag for "SPAN" omitted, but its declaration does not permit this
    Growing Economy Recent Figures</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 511, Column 81: start tag was here
    …Overheated-Economy-and-Economics.pdf"><span style='font-size:11.0pt;color:blue…
  • Error Line 518, Column 105: required attribute "ALT" not specified
    ….com/blog1/wp-content/uploads/2011/05/HedaseDam.jpg" width="140" align="right">

    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 521, Column 4: end tag for "SPAN" omitted, but its declaration does not permit this
    </a></b></span><br><span style='font-size:10.0pt;color:black'>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 519, Column 74: start tag was here
    …eekHornAfrica/morewha.php?wi=867#870"><span style='font-size:11.0pt;color:blue…
  • Error Line 521, Column 15: end tag for element "SPAN" which is not open
    </a></b></span><br><span style='font-size:10.0pt;color:black'>

    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 529, Column 4: end tag for "SPAN" omitted, but its declaration does not permit this
    </a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 527, Column 75: start tag was here
    …icles/The-Coup-Fiasco-in-Eritrea.pdf"><span style='font-size:11.0pt;color:blue…
  • Error Line 529, Column 15: end tag for element "SPAN" which is not open
    </a></b></span><br>

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

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

  • Error Line 535, Column 164: end tag for "SPAN" omitted, but its declaration does not permit this
    …#4776;&#4811;&#4669;&#4757;&#4877;&#4720;&#4757; &#4850;&#4658;</b></span>.....
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 534, Column 4: start tag was here
    <b><span style='font-size:11.0pt;color:blue'>
  • Error Line 535, Column 171: end tag for element "SPAN" which is not open
    …#4776;&#4811;&#4669;&#4757;&#4877;&#4720;&#4757; &#4850;&#4658;</b></span>.....

    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 536, Column 102: end tag for "SPAN" omitted, but its declaration does not permit this
    …-index.php"><span style='font-size:11.0pt;color:red'>for more</a></b><span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 536, Column 50: start tag was here
    …"http://aigaforum.com/geez-index.php"><span style='font-size:11.0pt;color:red'…
  • Error Line 539, Column 87: end tag for "SPAN" omitted, but its declaration does not permit this
    … Arabia accuses Ethiopia of posing threats to Sudan & Egypt</a></b></span>.....
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 538, Column 87: start tag was here
    …udi-on-hedase-dam-stupid-comment.pdf"><span style='font-size:11.0pt;color:blue…
  • Error Line 545, Column 20: end tag for "SPAN" omitted, but its declaration does not permit this
    Defining Heroism</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 544, Column 61: start tag was here
    …aforum.com/articles/Heroism_2013.pdf"><span style='font-size:11.0pt;color:blue…
  • Error Line 545, Column 31: end tag for element "SPAN" which is not open
    Defining Heroism</a></b></span><br>

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

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

  • Error Line 551, Column 89: end tag for "SPAN" omitted, but its declaration does not permit this
    …tion on  The Reporter, 6th Feb 2013</a></b></span><br><span style='font-size:1…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 550, Column 105: start tag was here
    …n-reporter-demand-meles-pictures.pdf"><span style='font-size:11.0pt;color:blue…
  • Error Line 551, Column 100: end tag for element "SPAN" which is not open
    …e Reporter, 6th Feb 2013</a></b></span><br><span style='font-size:10.0pt;color…

    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 556, Column 96: end tag for "SPAN" omitted, but its declaration does not permit this
    …my of Public Corruption in Ethiopia: Meles Zenawi Revisited </a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 555, Column 86: start tag was here
    …olitical-economy-meles-revisited.pdf"><span style='font-size:11.0pt;color:blue…
  • Error Line 556, Column 107: end tag for element "SPAN" which is not open
    …my of Public Corruption in Ethiopia: Meles Zenawi Revisited </a></b></span><br>

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

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

  • Error Line 559, Column 70: end tag for "SPAN" omitted, but its declaration does not permit this
    …ia's Strategic Resolve to Building the Grand Renaissance Dam</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 558, Column 66: start tag was here
    …m.com/articles/grand-dam-resolve.php"><span style='font-size:11.0pt;color:blue…
  • Error Line 559, Column 81: end tag for element "SPAN" which is not open
    …ia's Strategic Resolve to Building the Grand Renaissance Dam</a></b></span><br>

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

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

  • Error Line 564, Column 150: end tag for "SPAN" omitted, but its declaration does not permit this
    …&#4773;&#4661;&#4776; &#4768;&#4850;&#4661; &#4768;&#4704;&#4707;</b></span>...
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 563, Column 4: start tag was here
    <b><span style='font-size:11.0pt;color:blue'>
  • Error Line 564, Column 157: end tag for element "SPAN" which is not open
    …&#4773;&#4661;&#4776; &#4768;&#4850;&#4661; &#4768;&#4704;&#4707;</b></span>...

    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 565, Column 103: end tag for "SPAN" omitted, but its declaration does not permit this
    …ex.php"><span style='font-size:11.0pt;color:red'>for more</a></b><span><br><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 565, Column 51: start tag was here
    …"http://aigaforum.com/geez-index.php"><span style='font-size:11.0pt;color:red'…
  • Error Line 568, Column 57: end tag for "SPAN" omitted, but its declaration does not permit this
    &#4768;&#4939;&#4941; &#4619;&#4845; &#4678;&#4635; …</b></span>....
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 567, Column 4: start tag was here
    <b><span style='font-size:11.0pt;color:blue'>
  • Error Line 569, Column 103: end tag for "SPAN" omitted, but its declaration does not permit this
    …ex.php"><span style='font-size:11.0pt;color:red'>for more</a></b><span><br><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 569, Column 51: start tag was here
    …"http://aigaforum.com/geez-index.php"><span style='font-size:11.0pt;color:red'…
  • Error Line 574, Column 55: required attribute "ALT" not specified
    <img src="http://aigaforum.com/geez-page.jpg" border=0>

    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 581, Column 16: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <div align=left>

    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 583, Column 25: document type does not allow element "UL" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <span class="footer"><ul><font color=black>

    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 583, Column 43: start tag for "LI" omitted, but its declaration does not permit this
    <span class="footer"><ul><font color=black>
  • Error Line 585, Column 4: document type does not allow element "LI" here
    <li><b><a href="http://aigaforum.com/news/bloomberg-on-metal-eng.php"><span sty…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 585, Column 150: end tag for "SPAN" omitted, but its declaration does not permit this
    …t-size:10.0pt;color:blue'>METEC Seeks More Foreign Partners </a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 585, Column 71: start tag was here
    ….com/news/bloomberg-on-metal-eng.php"><span style='font-size:10.0pt;color:blue…
  • Error Line 585, Column 161: end tag for "FONT" omitted, but its declaration does not permit this
    …t-size:10.0pt;color:blue'>METEC Seeks More Foreign Partners </a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 583, Column 26: start tag was here
    <span class="footer"><ul><font color=black>
  • Error Line 585, Column 161: end tag for "UL" omitted, but its declaration does not permit this
    …t-size:10.0pt;color:blue'>METEC Seeks More Foreign Partners </a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 583, Column 22: start tag was here
    <span class="footer"><ul><font color=black>
  • Error Line 587, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/afar-drought-update-2013.pdf"><sp…

    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 587, Column 191: end tag for "SPAN" omitted, but its declaration does not permit this
    …g Effects of no Rain In Afar Region's Drought- Belt District</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 587, Column 77: start tag was here
    …rticles/afar-drought-update-2013.pdf"><span style='font-size:10.0pt;color:blue…
  • Error Line 587, Column 202: end tag for "DIV" omitted, but its declaration does not permit this
    …g Effects of no Rain In Afar Region's Drought- Belt District</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 581, Column 1: start tag was here
    <div align=left>
  • Error Line 589, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/Ethiopia-strides-forward.pdf "><s…

    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 589, Column 190: end tag for "SPAN" omitted, but its declaration does not permit this
    …rward despite neoliberals' cynicism</a></b></span><br>Fantahun Belay Feb 18, 2…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 589, Column 78: start tag was here
    …ticles/Ethiopia-strides-forward.pdf "><span style='font-size:10.0pt;color:blue…
  • Error Line 589, Column 201: end tag for element "SPAN" which is not open
    …despite neoliberals' cynicism</a></b></span><br>Fantahun Belay Feb 18, 2013<br>

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

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

  • Error Line 593, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/gtp-strong-wind-of-change.pdf"><s…

    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 593, Column 145: end tag for "SPAN" omitted, but its declaration does not permit this
    …n style='font-size:10.0pt;color:blue'>Strong winds of change</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 593, Column 78: start tag was here
    …ticles/gtp-strong-wind-of-change.pdf"><span style='font-size:10.0pt;color:blue…
  • Error Line 593, Column 156: end tag for element "SPAN" which is not open
    …n style='font-size:10.0pt;color:blue'>Strong winds of change</a></b></span><br>

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

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

  • Error Line 599, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/news/ethio-tropical-gypsum.php"><span styl…

    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 599, Column 201: end tag for "SPAN" omitted, but its declaration does not permit this
    …ed by Diaspora Ethiopians from the USA Inaugurated In Tigrai</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 599, Column 70: start tag was here
    …m.com/news/ethio-tropical-gypsum.php"><span style='font-size:10.0pt;color:blue…
  • Error Line 599, Column 212: end tag for element "SPAN" which is not open
    …ed by Diaspora Ethiopians from the USA Inaugurated In Tigrai</a></b></span><br>

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

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

  • Error Line 601, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://hebrezema.info/Fund-Raised-by-Ethiopian-in-Denmark-Aarhu…

    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 601, Column 176: end tag for "SPAN" omitted, but its declaration does not permit this
    ….0pt;color:blue'>Fund Raised by Ethiopians in Denmark Aarhus</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 601, Column 88: start tag was here
    …-by-Ethiopian-in-Denmark-Aarhus.html"><span style='font-size:11.0pt;color:blue…
  • Error Line 601, Column 187: end tag for element "SPAN" which is not open
    ….0pt;color:blue'>Fund Raised by Ethiopians in Denmark Aarhus</a></b></span><br>

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

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

  • Error Line 603, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/From-Economic-Dependency-to-Democ…

    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 603, Column 229: end tag for "SPAN" omitted, but its declaration does not permit this
    …n to Democratic Developmental State</a></b></span><br>Desta, Asayehgn Ph.D Feb…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 603, Column 111: start tag was here
    …o-Democratic-Developmental-State.pdf"><span style='font-size:10.0pt;color:blue…
  • Error Line 603, Column 240: end tag for element "SPAN" which is not open
    …ocratic Developmental State</a></b></span><br>Desta, Asayehgn Ph.D Feb 16, 2013

    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 607, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li>

    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 608, Column 155: end tag for "SPAN" omitted, but its declaration does not permit this
    …An Unorthodox Idea for the Tewahdo </a></b></span><br>Entehabu Berhe Feb 13, 2…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 608, Column 75: start tag was here
    …icles/unorthodoxidea-for-tewahdo.php"><span style='font-size:10.0pt;color:blue…
  • Error Line 608, Column 166: end tag for element "SPAN" which is not open
    …rthodox Idea for the Tewahdo </a></b></span><br>Entehabu Berhe Feb 13, 2013<br>

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

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

  • Error Line 610, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/news/Agreement-Signed-between-Ethiopia-and…

    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 610, Column 196: end tag for "SPAN" omitted, but its declaration does not permit this
    …'>Ethiopia And UNCTAD Signed Technical Cooperation Agreement</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 610, Column 93: start tag was here
    …gned-between-Ethiopia-and-UNCTAD.pdf"><span style='font-size:10.0pt;color:blue…
  • Error Line 610, Column 207: end tag for element "SPAN" which is not open
    …'>Ethiopia And UNCTAD Signed Technical Cooperation Agreement</a></b></span><br>

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

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

  • Error Line 613, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/meles-the-strategist-part2.php"><…

    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 613, Column 182: end tag for "SPAN" omitted, but its declaration does not permit this
    …'>Meles Zenawi: A dove of peace and a military strategist II</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 613, Column 79: start tag was here
    …icles/meles-the-strategist-part2.php"><span style='font-size:10.0pt;color:blue…
  • Error Line 613, Column 193: end tag for element "SPAN" which is not open
    …'>Meles Zenawi: A dove of peace and a military strategist II</a></b></span><br>

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

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

  • Error Line 619, Column 5: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
     <li> <b><a href="http://www.bloomberg.com/news/print/2013-02-11/ethiopia-coaxe…

    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 620, Column 110: end tag for "SPAN" omitted, but its declaration does not permit this
    …opia Coaxes Investors as It Struggles to Finance Growth Plan</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 620, Column 1: start tag was here
    <span style='font-size:10.0pt;color:blue'>Ethiopia Coaxes Investors as It Strug…
  • Error Line 620, Column 121: end tag for element "SPAN" which is not open
    …opia Coaxes Investors as It Struggles to Finance Growth Plan</a></b></span><br>

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

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

  • Error Line 623, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/meles-the-strategist.php"><span s…

    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 623, Column 173: end tag for "SPAN" omitted, but its declaration does not permit this
    … of peace and a military strategist</a></b></span><br>Sani Awol Feb 11, 2013<b…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 623, Column 73: start tag was here
    …om/articles/meles-the-strategist.php"><span style='font-size:10.0pt;color:blue…
  • Error Line 623, Column 184: end tag for element "SPAN" which is not open
    …of peace and a military strategist</a></b></span><br>Sani Awol Feb 11, 2013<br>

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

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

  • Error Line 626, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/our-heroes-and-heroines-deserve-m…

    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 626, Column 184: end tag for "SPAN" omitted, but its declaration does not permit this
    …and heroines deserve a war memorial</a></b></span><br>Eyassu Ephraim Feb 11, 2…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 626, Column 93: start tag was here
    …es-and-heroines-deserve-memorial.pdf"><span style='font-size:10.0pt;color:blue…
  • Error Line 626, Column 195: end tag for element "SPAN" which is not open
    …roines deserve a war memorial</a></b></span><br>Eyassu Ephraim Feb 11, 2013<br>

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

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

  • Error Line 628, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/national-income-account.pdf"><spa…

    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 628, Column 183: end tag for "SPAN" omitted, but its declaration does not permit this
    …Payment and Current Account Balance</a></b></span><br>Grenchal Zharina  Feb 11…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 628, Column 76: start tag was here
    …articles/national-income-account.pdf"><span style='font-size:10.0pt;color:blue…
  • Error Line 628, Column 194: end tag for element "SPAN" which is not open
    …nd Current Account Balance</a></b></span><br>Grenchal Zharina  Feb 11, 2013<br>

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

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

  • Error Line 630, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/ethiopia-and-ngo.pdf"><span style…

    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 630, Column 176: end tag for "SPAN" omitted, but its declaration does not permit this
    …hiopia: Drums and Rhythms of the International Value Warfare</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 630, Column 69: start tag was here
    …um.com/articles/ethiopia-and-ngo.pdf"><span style='font-size:10.0pt;color:blue…
  • Error Line 630, Column 187: end tag for element "SPAN" which is not open
    …hiopia: Drums and Rhythms of the International Value Warfare</a></b></span><br>

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

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

  • Error Line 636, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/accolade-defense-forces.php"><spa…

    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 636, Column 185: end tag for "SPAN" omitted, but its declaration does not permit this
    …nse Forces Day: Perfect Accolade To Our Revered Institution.</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 636, Column 76: start tag was here
    …articles/accolade-defense-forces.php"><span style='font-size:10.0pt;color:blue…
  • Error Line 636, Column 196: end tag for element "SPAN" which is not open
    …nse Forces Day: Perfect Accolade To Our Revered Institution.</a></b></span><br>

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

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

  • Error Line 638, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/on-eritrea-au-speech-2013.php">

    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 639, Column 107: end tag for "SPAN" omitted, but its declaration does not permit this
    …onfusing and contradictory: Eritrea’s intervention at the AU</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 639, Column 1: start tag was here
    <span style='font-size:10.0pt;color:blue'>Confusing and contradictory: Eritrea’…
  • Error Line 639, Column 118: end tag for element "SPAN" which is not open
    …onfusing and contradictory: Eritrea’s intervention at the AU</a></b></span><br>

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

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

  • Error Line 642, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/reply-to-constitution-uni.php"><s…

    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 643, Column 72: end tag for "SPAN" omitted, but its declaration does not permit this
    …al Secession: A Response to Fiseha </a></b></span><br>TegbaruYared Feb 8, 2013…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 642, Column 78: start tag was here
    …ticles/reply-to-constitution-uni.php"><span style='font-size:10.0pt;color:blue…
  • Error Line 643, Column 83: end tag for element "SPAN" which is not open
    …Secession: A Response to Fiseha </a></b></span><br>TegbaruYared Feb 8, 2013<br>

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

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

  • Error Line 644, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/news/deputy-pm-worldbank-dc.php">

    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 645, Column 105: end tag for "SPAN" omitted, but its declaration does not permit this
    … Discusses Success of Ethiopia's...</a></b></span><br>Tsehaye Debalekew Feb 06…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 645, Column 1: start tag was here
    <span style='font-size:10.0pt;color:blue'>Ethiopian Deputy Premier Discusses Su…
  • Error Line 645, Column 116: end tag for element "SPAN" which is not open
    …s Success of Ethiopia's...</a></b></span><br>Tsehaye Debalekew Feb 06, 2013<br>

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

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

  • Error Line 647, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/zeray-interview-seyoum.php"><span…

    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 648, Column 90: end tag for "SPAN" omitted, but its declaration does not permit this
    …le about the way the west perceive Africa-China Relationship</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 647, Column 75: start tag was here
    …/articles/zeray-interview-seyoum.php"><span style='font-size:10.0pt;color:blue…
  • Error Line 648, Column 101: end tag for element "SPAN" which is not open
    …le about the way the west perceive Africa-China Relationship</a></b></span><br>

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

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

  • Error Line 649, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://www.aigaforum.com/articles/Ethiopia-Multicultural-Educat…

    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 650, Column 65: end tag for "SPAN" omitted, but its declaration does not permit this
    …ducation: A Negation to the Past...</a></b></span><br>Mahari Yohans Feb 4, 201…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 649, Column 89: start tag was here
    …Ethiopia-Multicultural-Education.pdf"><span style='font-size:10.0pt;color:blue…
  • Error Line 650, Column 76: end tag for element "SPAN" which is not open
    …tion: A Negation to the Past...</a></b></span><br>Mahari Yohans Feb 4, 2013<br>

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

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

  • Error Line 652, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/theory-and-practice-of-meles-zena…

    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 652, Column 181: end tag for "SPAN" omitted, but its declaration does not permit this
    …iew Article The Theory and practice of Meles</a></b></span><br>ALEX DE WAAL<br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 652, Column 89: start tag was here
    …ry-and-practice-of-meles-zenawi.pdf "><span style='font-size:10.0pt;color:blue…
  • Error Line 652, Column 192: end tag for element "SPAN" which is not open
    …iew Article The Theory and practice of Meles</a></b></span><br>ALEX DE WAAL<br>

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

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

  • Error Line 654, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li>

    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 656, Column 65: end tag for "SPAN" omitted, but its declaration does not permit this
    Deputy Prime Minister meets Gordon Brown, UK Parliamentarians</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 655, Column 79: start tag was here
    …puty-prime-minister-meets-gordon.pdf"><span style='font-size:10.0pt;color:blue…
  • Error Line 656, Column 76: end tag for element "SPAN" which is not open
    Deputy Prime Minister meets Gordon Brown, UK Parliamentarians</a></b></span><br>

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

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

  • Error Line 659, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li>

    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 661, Column 29: end tag for "SPAN" omitted, but its declaration does not permit this
    The Difference is visible</a></b></span><br>Mohammed Nassir Jan 30, 2013<br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 660, Column 63: start tag was here
    …orum.com/articles/visible-change.php"><span style='font-size:10.0pt;color:blue…
  • Error Line 661, Column 40: end tag for element "SPAN" which is not open
    The Difference is visible</a></b></span><br>Mohammed Nassir Jan 30, 2013<br>

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

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

  • Error Line 663, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a href="http://aigaforum.com/articles/Prognosis-of-tplf.pdf"><span styl…

    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 664, Column 62: end tag for "SPAN" omitted, but its declaration does not permit this
    Prognosis on the Logic of the Tigrian Struggle (1975—1991)</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 663, Column 70: start tag was here
    …m.com/articles/Prognosis-of-tplf.pdf"><span style='font-size:10.0pt;color:blue…
  • Error Line 664, Column 73: end tag for element "SPAN" which is not open
    Prognosis on the Logic of the Tigrian Struggle (1975—1991)</a></b></span><br>

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

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

  • Error Line 666, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><b><a 

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

  • Warning Line 671, Column 1: unclosed start-tag requires SHORTTAG YES
    </li></ul>

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

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

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

  • Info Line 666, Column 8: start tag was here
    <li><b><a 
  • Error Line 671, Column 5: end tag for "B" omitted, but its declaration does not permit this
    </li></ul>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 666, Column 5: start tag was here
    <li><b><a 
  • Error Line 671, Column 10: end tag for element "UL" which is not open
    </li></ul>

    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 672, Column 4: end tag for element "B" which is not open
    </b><img src="images/hr_main.gif" alt="" width="450" height="8"><br>

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

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

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

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

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

  • Error Line 689, Column 18: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <div align=center>

    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 694, Column 78: required attribute "ALT" not specified
    <img src="http://aigaforum.com/images/live-radio.jpg" width="130" align=right>

    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 696, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 697, Column 101: end tag for "SPAN" omitted, but its declaration does not permit this
    …e.com:8000/stream"><span style='font-size:10.0pt;color:blue'>DWT</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 697, Column 53: start tag was here
    …tp://www.dmtsiweyane.com:8000/stream"><span style='font-size:10.0pt;color:blue…
  • Error Line 697, Column 112: end tag for "TABLE" omitted, but its declaration does not permit this
    …e.com:8000/stream"><span style='font-size:10.0pt;color:blue'>DWT</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 690, Column 1: start tag was here
    <TABLE WIDTH="250" BGCOLOR="#FFCC99" CELLSPACING="0" CELLPADDING="0"  BORDER="0…
  • Error Line 697, Column 112: end tag for "DIV" omitted, but its declaration does not permit this
    …e.com:8000/stream"><span style='font-size:10.0pt;color:blue'>DWT</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 689, Column 1: start tag was here
    <div align=center>
  • Error Line 699, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 700, Column 103: end tag for "SPAN" omitted, but its declaration does not permit this
    …ational.html"><span style='font-size:10.0pt;color:blue'>ET.R</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 700, Column 54: start tag was here
    …p://www.etvlive.gov.et/national.html"><span style='font-size:10.0pt;color:blue…
  • Error Line 700, Column 114: end tag for element "SPAN" which is not open
    …ational.html"><span style='font-size:10.0pt;color:blue'>ET.R</a></b></span><br>

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

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

  • Error Line 702, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 703, Column 101: end tag for "SPAN" omitted, but its declaration does not permit this
    …v.et/fm97.1.html"><span style='font-size:10.0pt;color:blue'>FM97</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 703, Column 52: start tag was here
    …ttp://www.etvlive.gov.et/fm97.1.html"><span style='font-size:10.0pt;color:blue…
  • Error Line 703, Column 112: end tag for element "SPAN" which is not open
    …v.et/fm97.1.html"><span style='font-size:10.0pt;color:blue'>FM97</a></b></span>

    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 706, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 707, Column 90: end tag for "SPAN" omitted, but its declaration does not permit this
    …com/Live"><span style='font-size:10.0pt;color:blue'>FANA</a></b></span><br><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 707, Column 41: start tag was here
    …><a href="http://www.fanabc.com/Live"><span style='font-size:10.0pt;color:blue…
  • Error Line 707, Column 101: end tag for element "SPAN" which is not open
    …com/Live"><span style='font-size:10.0pt;color:blue'>FANA</a></b></span><br><br>

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

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

  • Error Line 709, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 710, Column 107: end tag for "SPAN" omitted, but its declaration does not permit this
    …el/erena-online"><span style='font-size:10.0pt;color:blue'>ERENA</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 710, Column 57: start tag was here
    …/www.ustream.tv/channel/erena-online"><span style='font-size:10.0pt;color:blue…
  • Error Line 710, Column 118: end tag for element "SPAN" which is not open
    …el/erena-online"><span style='font-size:10.0pt;color:blue'>ERENA</a></b></span>

    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 714, Column 15: end tag for element "SPAN" which is not open
    </TABLE></span>

    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 715, Column 6: end tag for element "DIV" which is not open
    </div>

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

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

  • Error Line 717, Column 26: document type does not allow element "SPAN" here; missing one of "TH", "TD" start-tag
    <tr> <span class="footer">

    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 719, Column 39: document type does not allow element "TD" here
      <td align="center" bgcolor="#FF0000"><font color=white><b>Mark Your Calendar<…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 721, Column 15: end tag for "SPAN" omitted, but its declaration does not permit this
              </tr>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 717, Column 6: start tag was here
    <tr> <span class="footer">
  • Error Line 721, Column 15: 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 729, Column 18: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <div align=center>

    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 734, Column 22: required attribute "ALT" not specified
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 734, Column 26: end tag for "SPAN" omitted, but its declaration does not permit this
    height="110" border=0></a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 732, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>
  • Error Line 734, Column 37: end tag for "DIV" omitted, but its declaration does not permit this
    height="110" border=0></a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 729, Column 1: start tag was here
    <div align=center>
  • Error Line 735, Column 70: end tag for element "DIV" which is not open
    <br><img src="images/hr_main.gif" alt="" width="220" height="8"></div>

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

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

  • Error Line 751, Column 95: required attribute "ALT" not specified
    …m/images/tsenat-radio.jpg" width="90" height="100" align=left><div align=right>

    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 753, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 755, Column 54: end tag for "SPAN" omitted, but its declaration does not permit this
    <span style='font-size:10.0pt;color:blue'>02-23-13</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 755, Column 1: start tag was here
    <span style='font-size:10.0pt;color:blue'>02-23-13</a></b></span><br>
  • Error Line 755, Column 65: end tag for element "SPAN" which is not open
    <span style='font-size:10.0pt;color:blue'>02-23-13</a></b></span><br>

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

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

  • Error Line 759, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 761, Column 55: end tag for "SPAN" omitted, but its declaration does not permit this
    <span style='font-size:10.0pt;color:brown'>02-16-13</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 761, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>02-16-13</a></b></span><br>
  • Error Line 761, Column 66: end tag for element "SPAN" which is not open
    <span style='font-size:10.0pt;color:brown'>02-16-13</a></b></span><br>

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

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

  • Error Line 764, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 766, Column 55: end tag for "SPAN" omitted, but its declaration does not permit this
    <span style='font-size:10.0pt;color:brown'>02-09-13</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 766, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>02-09-13</a></b></span><br>
  • Error Line 766, Column 66: end tag for element "SPAN" which is not open
    <span style='font-size:10.0pt;color:brown'>02-09-13</a></b></span><br>

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

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

  • Error Line 769, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 771, Column 55: end tag for "SPAN" omitted, but its declaration does not permit this
    <span style='font-size:10.0pt;color:brown'>02-02-13</a></b></span>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 771, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>02-02-13</a></b></span>
  • Error Line 771, Column 66: end tag for element "SPAN" which is not open
    <span style='font-size:10.0pt;color:brown'>02-02-13</a></b></span>

    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 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 776, Column 55: end tag for "SPAN" omitted, but its declaration does not permit this
    <span style='font-size:10.0pt;color:brown'>01-26-13</a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 776, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>01-26-13</a></b></span><br>
  • Error Line 776, Column 66: end tag for element "SPAN" which is not open
    <span style='font-size:10.0pt;color:brown'>01-26-13</a></b></span><br>

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

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

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

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

  • Info Line 749, Column 1: start tag was here
    <div align=center>
  • Error Line 800, Column 22: required attribute "ALT" not specified
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 800, Column 26: end tag for "SPAN" omitted, but its declaration does not permit this
    height="110" border=0></a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 798, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>
  • Error Line 800, Column 37: end tag for element "SPAN" which is not open
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 810, Column 22: required attribute "ALT" not specified
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 810, Column 26: end tag for "SPAN" omitted, but its declaration does not permit this
    height="110" border=0></a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 808, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>
  • Error Line 810, Column 37: end tag for element "SPAN" which is not open
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 823, Column 22: required attribute "ALT" not specified
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 823, Column 26: end tag for "SPAN" omitted, but its declaration does not permit this
    height="110" border=0></a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 821, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>
  • Error Line 823, Column 37: end tag for element "SPAN" which is not open
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 836, Column 22: required attribute "ALT" not specified
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 836, Column 26: end tag for "SPAN" omitted, but its declaration does not permit this
    height="110" border=0></a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 834, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>
  • Error Line 836, Column 37: end tag for element "SPAN" which is not open
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 846, Column 22: required attribute "ALT" not specified
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 846, Column 26: end tag for "SPAN" omitted, but its declaration does not permit this
    height="110" border=0></a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 844, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>
  • Error Line 846, Column 37: end tag for element "SPAN" which is not open
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 857, Column 22: required attribute "ALT" not specified
    height="110" border=0></a></b></span><br>

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

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

  • Error Line 857, Column 26: end tag for "SPAN" omitted, but its declaration does not permit this
    height="110" border=0></a></b></span><br>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 855, Column 1: start tag was here
    <span style='font-size:10.0pt;color:brown'>
  • Error Line 858, Column 70: end tag for "B" omitted, but its declaration does not permit this
    <br><img src="images/hr_main.gif" alt="" width="220" height="8"></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 853, Column 1: start tag was here
    <b><span style='font-size:12.0pt;color:blue'><b><span style='font-size:12.0pt;c…
  • Error Line 874, Column 10: end tag for element "TABLE" which is not open
    		</table>

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

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

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

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

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

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

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

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

  • Error Line 877, Column 5: document type does not allow element "TR" here
    	<tr><td style="background-color:ivory;padding:0;margin:0;">

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 878, Column 51: duplicate specification of attribute "BGCOLOR"
    …idth="100%" BGCOLOR="#CfFFFC" BGCOLOR="#CCFFCC border="1" cellspacing="0" cell…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 878, Column 52: literal is missing closing delimiter
    …dth="100%" BGCOLOR="#CfFFFC" BGCOLOR="#CCFFCC border="1" cellspacing="0" cellp…

    Did you forget to close a (double) quote mark?

  • Error Line 878, Column 69: character data is not allowed here
    …R="#CfFFFC" BGCOLOR="#CCFFCC border="1" cellspacing="0" cellpadding="0" stylee…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 887, Column 18: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <div align=center><span class="footer">

    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 897, Column 77: end tag for "FONT" omitted, but its declaration does not permit this
    …ef="http://aigaforum.com/blog1/"><font color=blue>AigaBlog &nbsp</a></b>|&nbsp;
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 897, Column 43: start tag was here
    …<a href="http://aigaforum.com/blog1/"><font color=blue>AigaBlog &nbsp</a></b>|…
  • Error Line 946, Column 35: end tag for "FONT" omitted, but its declaration does not permit this
    <font color=blue> Ethiothisweek</a></font>|&nbsp;&nbsp
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 946, Column 1: start tag was here
    <font color=blue> Ethiothisweek</a></font>|&nbsp;&nbsp
  • Error Line 946, Column 42: end tag for "SPAN" omitted, but its declaration does not permit this
    <font color=blue> Ethiothisweek</a></font>|&nbsp;&nbsp
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 931, Column 1: start tag was here
    <span class="footer">
  • Error Line 946, Column 42: end tag for "SPAN" omitted, but its declaration does not permit this
    <font color=blue> Ethiothisweek</a></font>|&nbsp;&nbsp
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 887, Column 19: start tag was here
    <div align=center><span class="footer">
  • Error Line 946, Column 42: end tag for "DIV" omitted, but its declaration does not permit this
    <font color=blue> Ethiothisweek</a></font>|&nbsp;&nbsp
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 887, Column 1: start tag was here
    <div align=center><span class="footer">
  • Error Line 953, Column 81: end tag for "FONT" omitted, but its declaration does not permit this
    …thiopiafirst.com/" target="_blank"> <font color=blue>Ben</a></font>|&nbsp;&nbsp
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 953, Column 58: start tag was here
    ….ethiopiafirst.com/" target="_blank"> <font color=blue>Ben</a></font>|&nbsp;&n…
  • Error Line 953, Column 88: end tag for element "FONT" which is not open
    …thiopiafirst.com/" target="_blank"> <font color=blue>Ben</a></font>|&nbsp;&nbsp

    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 965, Column 65: end tag for "FONT" omitted, but its declaration does not permit this
     <a href="http://www.2merkato.com/"><font color=blue>2merkato</a></font>|&nbsp
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 965, Column 37: start tag was here
     <a href="http://www.2merkato.com/"><font color=blue>2merkato</a></font>|&nbsp
  • Error Line 965, Column 72: end tag for element "FONT" which is not open
     <a href="http://www.2merkato.com/"><font color=blue>2merkato</a></font>|&nbsp

    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 979, Column 51: document type does not allow element "A" here
    …p://www.selambus.com/" target="_blank"><font color=blue>Selambus</font></a>&nb…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 982, Column 47: document type does not allow element "A" here
    …"http://www.mu.edu.et" target="_blank"> <font color=blue>MU </font></a>&nbsp| …

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 983, Column 53: document type does not allow element "A" here
    …//www.radaonline.org/" target="_blank"> <font color=blue>Rada</font></a>&nbsp|…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 985, Column 65: document type does not allow element "A" here
    …://www.queenshebainternational.org/"target="_blank"><font color=blue>QueenSheba

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 986, Column 4: end tag for "FONT" omitted, but its declaration does not permit this
    </a>|</font>&nbsp;&nbsp
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 985, Column 66: start tag was here
    …://www.queenshebainternational.org/"target="_blank"><font color=blue>QueenSheba
  • Error Line 987, Column 49: document type does not allow element "A" here
     <a href="http://www.axumalumniassociations.com"><font color=blue>Axum 

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 989, Column 39: document type does not allow element "A" here
    <a href="http://www.atseyohannes.org/"><font color=blue>AYAA 

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 992, Column 34: document type does not allow element "A" here
    <a href="http://www.awlaelo.org/"><font color=blue>Awlaelo 

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 996, Column 32: document type does not allow element "A" here
    <a href="http://www.agazi.net/"><font color=blue>Agazi 

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1000, Column 32: document type does not allow element "A" here
    <a href="http://www.dasna.org/"><font color=blue>Dasna 

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1003, Column 47: document type does not allow element "A" here
    …"http://www.etff.org/" target="_blank"><font color=blue>etff.org</font></a>&nb…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1004, Column 47: document type does not allow element "A" here
    …="http://akababi.org/" target="_blank"><font color=blue>akababi.com</font></a>…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1005, Column 35: document type does not allow element "A" here
    <a href="http://www.gibe3.com.et/"><font color=red> Gibe III</font></a>| 

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1008, Column 45: document type does not allow element "A" here
    …f="http://peacei.com/" target="_blank"><font color=blue>Peacei</font></a>&nbsp…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1012, Column 41: document type does not allow element "A" here
    … href="http://www.ethiopiancable.com/"><font color=blue>ENC</font></a>|&nbsp;&…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1013, Column 41: document type does not allow element "A" here
    …a href="http://www.adwaforafrica.org/"><font color=blue>adwaforafrica</font></…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1016, Column 69: document type does not allow element "A" here
    …happyinethiopia.org/"  target="_blank"><font color=blue>H.A.P.P.Y</font></a>&n…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1018, Column 83: document type does not allow element "A" here
    …"http://www.mekellecity.com/index.asp"> <font color=blue>Mekellecity.com</font…

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1021, Column 64: document type does not allow element "A" here
    …solomon.blogspot.com/" target="_blank"><font color=blue>Eyasu Blog</font></a> …

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

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer 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 1021, Column 110: end tag for "SPAN" omitted, but its declaration does not permit this
    …n.blogspot.com/" target="_blank"><font color=blue>Eyasu Blog</font></a> </font>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 1018, Column 15: start tag was here
                  <span class="footer"> <a href="http://www.mekellecity.com/index.a…
  • Error Line 1021, Column 110: end tag for "A" omitted, but its declaration does not permit this
    …n.blogspot.com/" target="_blank"><font color=blue>Eyasu Blog</font></a> </font>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 976, Column 18: start tag was here
    <font color=blue><a href="http://www.trhb.gov.et/"><font color=blue>Health Bure…
  • Warning Line 1022, Column 43: NET-enabling start-tag requires SHORTTAG YES
    …p;&nbsp <a href="http://zkreayder.org"/ target="_blank"> <font color=blue>Zkre…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1028, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">&nbsp

    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 1032, Column 47: required attribute "ALT" not specified
    <IMG src="http://aigaforum.com/Audio_logo.gif">&nbsp 

    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 1034, Column 40: end tag for element "B" which is not open
    "><font color=blue>Sheger</font></a></b>|&nbsp;&nbsp;

    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 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">

    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 1040, Column 48: required attribute "ALT" not specified
    …="http://aigaforum.com/Audio_logo.gif">&nbsp<a href="http://www.medalyamedia.c…

    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 1042, Column 47: required attribute "ALT" not specified
    …="http://aigaforum.com/Audio_logo.gif"><a href="http://www.addiszefen.com/" ta…

    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 1045, Column 47: required attribute "ALT" not specified
    …="http://aigaforum.com/Audio_logo.gif"><a href="http://www.gezategaru.com/" ta…

    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 1047, Column 63: required attribute "ALT" not specified
    …="http://aigaforum.com/Audio_logo.gif"><a href="http://www.addislive.com/modul…

    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 1047, Column 121: cannot generate system identifier for general entity "name"
    ….addislive.com/modules.php?op=modload&name=News&file=index&catid=1"> <font col…

    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 1047, Column 121: general entity "name" not defined and no default entity
    ….addislive.com/modules.php?op=modload&name=News&file=index&catid=1"> <font col…

    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.

  • Error Line 1047, Column 125: reference to entity "name" for which no system identifier could be generated
    …islive.com/modules.php?op=modload&name=News&file=index&catid=1"> <font color=b…

    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 1047, Column 120: entity was defined here
    …w.addislive.com/modules.php?op=modload&name=News&file=index&catid=1"> <font co…
  • Warning Line 1047, Column 131: cannot generate system identifier for general entity "file"
    ….com/modules.php?op=modload&name=News&file=index&catid=1"> <font color=blue>Ad…

    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 1047, Column 131: general entity "file" not defined and no default entity
    ….com/modules.php?op=modload&name=News&file=index&catid=1"> <font color=blue>Ad…

    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.

  • Error Line 1047, Column 135: reference to entity "file" for which no system identifier could be generated
    …/modules.php?op=modload&name=News&file=index&catid=1"> <font color=blue>Addisl…

    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 1047, Column 130: entity was defined here
    …e.com/modules.php?op=modload&name=News&file=index&catid=1"> <font color=blue>A…
  • Warning Line 1047, Column 142: cannot generate system identifier for general entity "catid"
    …s.php?op=modload&name=News&file=index&catid=1"> <font color=blue>Addislive</fo…

    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 1047, Column 142: general entity "catid" not defined and no default entity
    …s.php?op=modload&name=News&file=index&catid=1"> <font color=blue>Addislive</fo…

    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.

  • Error Line 1047, Column 147: reference to entity "catid" for which no system identifier could be generated
    …?op=modload&name=News&file=index&catid=1"> <font color=blue>Addislive</font></…

    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 1047, Column 141: entity was defined here
    …es.php?op=modload&name=News&file=index&catid=1"> <font color=blue>Addislive</f…
  • Error Line 1049, Column 47: required attribute "ALT" not specified
    …="http://aigaforum.com/Audio_logo.gif"><a href="http://www.wust1120.com/WUST/W…

    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 1050, Column 47: required attribute "ALT" not specified
    <img src="http://aigaforum.com/Audio_logo.gif">

    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 1051, Column 84: end tag for "FONT" omitted, but its declaration does not permit this
    …eofethiopia.com/"><font color=blue>Voice of Ethiopia</a></font>&nbsp;&nbsp     
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 1051, Column 47: start tag was here
    …="http://www.thevoiceofethiopia.com/"><font color=blue>Voice of Ethiopia</a></…
  • Error Line 1051, Column 91: end tag for element "FONT" which is not open
    …eofethiopia.com/"><font color=blue>Voice of Ethiopia</a></font>&nbsp;&nbsp     

    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 1052, Column 47: required attribute "ALT" not specified
    …="http://aigaforum.com/Audio_logo.gif"> <a href="http://www.ethiopianconsensus…

    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 1055, Column 44: required attribute "ALT" not specified
     <img src="http://aigaforum.com/Video2.gif">&nbsp 

    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 1059, Column 44: required attribute "ALT" not specified
    … src="http://aigaforum.com/Video2.gif">&nbsp <a href="http://www.ethiopian.tv/…

    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 1062, Column 43: required attribute "ALT" not specified
    … src="http://aigaforum.com/Video2.gif"><a href="http://DireTube.com/" target="…

    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 1065, Column 21: NET-enabling start-tag requires SHORTTAG YES
                  <http://aigaforum.com/img src="Video2.gif"> <a href="http://www.e…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1065, Column 21: element "HTTP:" undefined
                  <http://aigaforum.com/img src="Video2.gif"> <a href="http://www.e…

    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 1067, Column 57: required attribute "ALT" not specified
    … src="http://aigaforum.com/Video2.gif"><a href=" http://www.ethiopia.se/media/…

    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 1070, Column 57: required attribute "ALT" not specified
    … src="http://aigaforum.com/Video2.gif"><a href="http://www.tvzete.net/" target…

    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 1072, Column 57: required attribute "ALT" not specified
    … src="http://aigaforum.com/Video2.gif"><a href="http://www.ectv.org/" target="…

    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 1072, Column 119: end tag for element "FONT" which is not open
    ….gif"><a href="http://www.ectv.org/" target="_blank">ECTV</a></font>&nbsp;&nbsp

    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 1075, Column 57: required attribute "ALT" not specified
    … src="http://aigaforum.com/Video2.gif">&nbsp <a href="http://WWW.EBSTV.TV"> <f…

    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 1075, Column 150: end tag for element "SPAN" which is not open
    …p://WWW.EBSTV.TV"> <font color="#006600">EBS</font></a>|&nbsp;&nbsp </span><br>

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

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

  • Error Line 1081, Column 46: duplicate specification of attribute "BGCOLOR"
    …width="99%" BGCOLOR="#CfFFFC" BGCOLOR="#CCFFCC border="1" cellspacing="0" cell…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1081, Column 47: literal is missing closing delimiter
    …idth="99%" BGCOLOR="#CfFFFC" BGCOLOR="#CCFFCC border="1" cellspacing="0" cellp…

    Did you forget to close a (double) quote mark?

  • Error Line 1081, Column 64: character data is not allowed here
    …R="#CfFFFC" BGCOLOR="#CCFFCC border="1" cellspacing="0" cellpadding="0" stylee…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 1088, Column 103: end tag for element "B" which is not open
    …ownloads.htm"><font color=red>click to download geez</font></a>)</b>&nbsp;&nbsp

    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 1103, Column 101: end tag for element "FONT" which is not open
    …ref="http://www.mathworks.com/"><font color=blue>wiki-mathlab</font></a></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 1114, Column 7: end tag for element "SPAN" which is not open
    </span></td>

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

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

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

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

  • Info Line 878, Column 5: start tag was here
    				<table width="100%" BGCOLOR="#CfFFFC" BGCOLOR="#CCFFCC border="1" cellspaci…
  • Error Line 1122, Column 16: end tag for element "TABLE" which is not open
            </table></td>

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

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

  • Error Line 1122, Column 21: end tag for element "TD" which is not open
            </table></td>

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

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

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

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

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

  • Error Line 1127, Column 10: end tag for element "TABLE" which is not open
      </table>	</td></tr>

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

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

  • Error Line 1127, Column 16: end tag for element "TD" which is not open
      </table>	</td></tr>

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

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

  • Error Line 1127, Column 21: end tag for element "TR" which is not open
      </table>	</td></tr>

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

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

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

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

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

  • Error Line 1134, Column 88: required attribute "TYPE" not specified
    …://us.js2.yimg.com/us.js.yimg.com/lib/smb/js/hosting/cp/js_source/whv2_001.js">

    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 1136, Column 30: required attribute "TYPE" not specified
    <script language="javascript">geovisit();</script>

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

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

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

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

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

  • Error Line 1141, Column 13: end tag for element "DIV" which is not open
    	</div></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.

Visitor Analysis

Daily Visitor
  • 1.388 visits