xandan, khandan, aso, aso xandan, haftana, heftana,xendan heftane, kurdish news, kurdistan news, video, kurdish video, karikater, hewal, hawal, hewaly kurdistan, kurd ده‌نگوباس، هه‌واڵ، خه‌ندان، ئاسۆ، رۆژنامه‌ی ئاسۆ، هه‌فتانه‌، الاسبوعية، کوردستان، ڤیدیۆ، کورد، kurdsky ...

xendan.org
  • Domain Name
    xendan.org
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #14135
  • Page Size
    93.2 KB
  • Ip Address
    190.93.248.160
  • Heading
    H1: 6, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    53 GIF, 48 JPG, 41 PNG

Website Meta Analysis

  • Title
    خه‌ ندان - پێشه‌ نگین
  • Meta Keyword
    xandan, khandan, aso, aso xandan, haftana, heftana,xendan heftane, kurdish news, kurdistan news, video, kurdish video, karikater, hewal, hawal, hewaly kurdistan, kurd ده‌نگوباس، هه‌واڵ، خه‌ندان، ئاسۆ، رۆژنامه‌ی ئاسۆ، هه‌فتانه‌، الاسبوعية، کوردستان، ڤیدیۆ، کورد، kurdsky
  • Meta Description
    xandan, khandan, aso, aso xandan, haftana, heftana,xendan heftane, kurdish news, kurdistan news, video, kurdish video, karikater, hewal, hawal, hewaly kurdistan, kurd ده‌نگوباس، هه‌واڵ، خه‌ندان، ئاسۆ، رۆژنامه‌ی ئاسۆ، هه‌فتانه‌، الاسبوعية، کوردستان، ڤیدیۆ، کورد، kurdsky

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    190.93.248.160
  • Domain Age
    4 Years, 6 Months, 10 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from xendan.org.

HTML Analysis

  • server: cloudflare-nginx
  • date: Mon, 09 Sep 2013 14:41:43 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • cache-control: private
  • vary: Accept-Encoding
  • x-aspnet-version: 4.0.30319
  • x-powered-by: ASP.NET
  • cf-ray: ab4a413cf71059d
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Access to .ORG WHOIS information is provided to assist persons in
determining the contents of a domain name registration record in the
Public Interest Registry registry database. The data in this record is provided by
Public Interest Registry for informational purposes only, and Public Interest Registry does not
guarantee its accuracy. This service is intended only for query-based
access. You agree that you will use this data only for lawful purposes
and that, under no circumstances will you use this data to: (a) allow,
enable, or otherwise support the transmission by e-mail, telephone, or
facsimile of mass unsolicited, commercial advertising or solicitations
to entities other than the data recipient's own existing customers; or
(b) enable high volume, automated, electronic processes that send
queries or data to the systems of Registry Operator, a Registrar, or
Afilias except as reasonably necessary to register domain names or
modify existing registrations. All rights reserved. Public Interest Registry reserves
the right to modify these terms at any time. By submitting this query,
you agree to abide by this policy.

Domain ID:D153586586-LROR
Domain Name:XENDAN.ORG
Created On:13-Aug-2008 09:23:49 UTC
Last Updated On:17-Sep-2011 22:59:11 UTC
Expiration Date:13-Aug-2019 09:23:49 UTC
Sponsoring Registrar:Wild West Domains, LLC (R120-LROR)
Status:CLIENT DELETE PROHIBITED
Status:CLIENT RENEW PROHIBITED
Status:CLIENT TRANSFER PROHIBITED
Status:CLIENT UPDATE PROHIBITED
Registrant ID:CR92438548
Registrant Name:araz jamal
Registrant Organization:kurdsky
Registrant Street1:SEHEWAN main street
Registrant Street2:
Registrant Street3:
Registrant City:sulaimani
Registrant State/Province:
Registrant Postal Code:00964
Registrant Country:IQ
Registrant Phone:+964.7701931390
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant Email: email
Admin ID:CR92438552
Admin Name:araz jamal
Admin Organization:kurdsky
Admin Street1:SEHEWAN main street
Admin Street2:
Admin Street3:
Admin City:sulaimani
Admin State/Province:
Admin Postal Code:00964
Admin Country:IQ
Admin Phone:+964.7701931390
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin Email: email
Tech ID:CR92438550
Tech Name:araz jamal
Tech Organization:kurdsky
Tech Street1:SEHEWAN main street
Tech Street2:
Tech Street3:
Tech City:sulaimani
Tech State/Province:
Tech Postal Code:00964
Tech Country:IQ
Tech Phone:+964.7701931390
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech Email: email
Name Server:NS2.RACKSPACE.COM
Name Server:NS.RACKSPACE.COM
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
DNSSEC:Unsigned


DNS Analysis


DNS servers
ns.rackspace.com [69.20.95.4]
ns2.rackspace.com [65.61.188.4]


DNS Records

Answer records
xendan.org NS  ns2.rackspace.com 86400s
xendan.org NS  ns.rackspace.com 86400s
xendan.org MX
preference: 10
exchange: MX1.EMAILSRVR.com
86400s
xendan.org MX
preference: 20
exchange: MX2.EMAILSRVR.com
86400s
xendan.org A 31.222.130.236 86400s
xendan.org SOA
server: ns.rackspace.com
email: hostmaster@rackspace.com
serial: 1324448476
refresh: 3600
retry: 300
expire: 1814400
minimum ttl: 300
300s

Authority records

Additional records

IP 190.93.248.160 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 348 Errors
  • 400 Warnings
Ratio Text/Html
  • 0.6966254453992873
Message Error
  • Error Line 24, Column 12: there is no attribute "NAME"
    <meta NAME="Author" CONTENT="ARAZ JAMAL"/>

    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 24, Column 29: there is no attribute "CONTENT"
    <meta NAME="Author" CONTENT="ARAZ JAMAL"/>

    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 24, Column 42: required attribute "content" not specified
    <meta NAME="Author" CONTENT="ARAZ JAMAL"/>

    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 440, Column 25: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start menu head --->
  • Info Line 440, Column 1: comment declaration started here
    <!--- start menu head --->
  • Error Line 465, Column 23: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end menu head --->
  • Info Line 465, Column 1: comment declaration started here
    <!--- end menu head --->
  • Error Line 479, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- Start head --->
  • Info Line 479, Column 1: comment declaration started here
    <!--- Start head --->
  • Error Line 495, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start kash --->
  • Info Line 495, Column 1: comment declaration started here
    <!--- start kash --->
  • Error Line 686, Column 18: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end kash --->
  • Info Line 686, Column 1: comment declaration started here
    <!--- end kash --->
  • Error Line 702, Column 18: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- End head --->
  • Info Line 702, Column 1: comment declaration started here
    <!--- End head --->
  • Error Line 703, Column 22: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start reklam --->
  • Info Line 703, Column 1: comment declaration started here
    <!--- start reklam --->
  • Error Line 704, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end reklam --->
  • Info Line 704, Column 1: comment declaration started here
    <!--- end reklam --->
  • Error Line 707, Column 25: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start main menu --->
  • Info Line 707, Column 1: comment declaration started here
    <!--- start main menu --->
  • Error Line 720, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start menu --->
  • Info Line 720, Column 1: comment declaration started here
    <!--- start menu --->
  • Error Line 726, Column 32: there is no attribute "onMouseover"
    			<li><a href="#" onMouseover="cssdropdown.dropit(this,event,'hawal')"><span>ه…

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

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

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

  • Error Line 750, Column 18: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end menu --->
  • Info Line 750, Column 1: comment declaration started here
    <!--- end menu --->
  • Error Line 751, Column 24: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start dropmenu --->
  • Info Line 751, Column 1: comment declaration started here
    <!--- start dropmenu --->
  • Error Line 761, Column 22: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end dropmenu --->
  • Info Line 761, Column 1: comment declaration started here
    <!--- end dropmenu --->
  • Error Line 767, Column 23: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end main menu --->
  • Info Line 767, Column 1: comment declaration started here
    <!--- end main menu --->
  • Error Line 775, Column 30: invalid comment declaration: found name character outside comment but inside comment declaration
            <!--- start hewal2 --->
  • Info Line 775, Column 9: comment declaration started here
            <!--- start hewal2 --->
  • Error Line 784, Column 38: document type does not allow element "table" here; assuming missing "li" start-tag
    <table id="DataList2" cellspacing="0">
  • Error Line 787, Column 8: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…

    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 787, Column 37: cannot generate system identifier for general entity "jmara"
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…

    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 787, Column 37: general entity "jmara" not defined and no default entity
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…

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

  • Warning Line 787, Column 42: reference not terminated by REFC delimiter
    … <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd…

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

  • Warning Line 787, Column 42: reference to external entity in attribute value
    … <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd…

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

  • Error Line 787, Column 42: reference to entity "jmara" for which no system identifier could be generated
    … <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 787, Column 49: cannot generate system identifier for general entity "Jor"
    …  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd2822013…

    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 787, Column 49: general entity "Jor" not defined and no default entity
    …  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd2822013…

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

  • Warning Line 787, Column 52: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd2822013bbs…

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

  • Warning Line 787, Column 52: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd2822013bbs…

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

  • Error Line 787, Column 52: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd2822013bbs…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 792, Column 8: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
        <li><a  href="dreja.aspx?=hewal&jmara=51517&Jor=1"><img src="imgnews/anfal-…

    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 792, Column 42: reference not terminated by REFC delimiter
    … <li><a  href="dreja.aspx?=hewal&jmara=51517&Jor=1"><img src="imgnews/anfal-28…

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

  • Warning Line 792, Column 42: reference to external entity in attribute value
    … <li><a  href="dreja.aspx?=hewal&jmara=51517&Jor=1"><img src="imgnews/anfal-28…

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

  • Error Line 792, Column 42: reference to entity "jmara" for which no system identifier could be generated
    … <li><a  href="dreja.aspx?=hewal&jmara=51517&Jor=1"><img src="imgnews/anfal-28…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 792, Column 52: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51517&Jor=1"><img src="imgnews/anfal-28-2-2013-S.…

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

  • Warning Line 792, Column 52: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51517&Jor=1"><img src="imgnews/anfal-28-2-2013-S.…

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

  • Error Line 792, Column 52: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51517&Jor=1"><img src="imgnews/anfal-28-2-2013-S.…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 798, Column 8: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
        <li><a  href="dreja.aspx?=hewal&jmara=51515&Jor=2"><img src="imgnews/xendan…

    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 798, Column 42: reference not terminated by REFC delimiter
    … <li><a  href="dreja.aspx?=hewal&jmara=51515&Jor=2"><img src="imgnews/xendan 2…

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

  • Warning Line 798, Column 42: reference to external entity in attribute value
    … <li><a  href="dreja.aspx?=hewal&jmara=51515&Jor=2"><img src="imgnews/xendan 2…

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

  • Error Line 798, Column 42: reference to entity "jmara" for which no system identifier could be generated
    … <li><a  href="dreja.aspx?=hewal&jmara=51515&Jor=2"><img src="imgnews/xendan 2…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 798, Column 52: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51515&Jor=2"><img src="imgnews/xendan 24-2-Ss.jpg…

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

  • Warning Line 798, Column 52: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51515&Jor=2"><img src="imgnews/xendan 24-2-Ss.jpg…

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

  • Error Line 798, Column 52: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51515&Jor=2"><img src="imgnews/xendan 24-2-Ss.jpg…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 805, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 784, Column 1: start tag was here
    <table id="DataList2" cellspacing="0">
  • Error Line 813, Column 29: invalid comment declaration: found name character outside comment but inside comment declaration
            <!--- end  hewal2 --->
  • Info Line 813, Column 9: comment declaration started here
            <!--- end  hewal2 --->
  • Error Line 816, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start main --->
  • Info Line 816, Column 1: comment declaration started here
    <!--- start main --->
  • Error Line 821, Column 23: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start manshet --->
  • Info Line 821, Column 1: comment declaration started here
    <!--- start manshet --->
  • Warning Line 826, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51508&Jor=1" title="28/02/2013 ">

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

  • Warning Line 826, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51508&Jor=1" title="28/02/2013 ">

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

  • Error Line 826, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51508&Jor=1" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 826, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51508&Jor=1" title="28/02/2013 ">

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

  • Warning Line 826, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51508&Jor=1" title="28/02/2013 ">

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

  • Error Line 826, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51508&Jor=1" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 830, Column 40: required attribute "alt" not specified
    <img src="imgnews/kobemaw-28-2-b.jpg" />

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

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

  • Warning Line 834, Column 139: reference not terminated by REFC delimiter
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51508&Jor=1">درێژه...‌</a></span>

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

  • Warning Line 834, Column 139: reference to external entity in attribute value
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51508&Jor=1">درێژه...‌</a></span>

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

  • Error Line 834, Column 139: reference to entity "jmara" for which no system identifier could be generated
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51508&Jor=1">درێژه...‌</a></span>

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 834, Column 149: reference not terminated by REFC delimiter
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51508&Jor=1">درێژه...‌</a></span>

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

  • Warning Line 834, Column 149: reference to external entity in attribute value
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51508&Jor=1">درێژه...‌</a></span>

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

  • Error Line 834, Column 149: reference to entity "Jor" for which no system identifier could be generated
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51508&Jor=1">درێژه...‌</a></span>

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 840, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end manshet --->
  • Info Line 840, Column 1: comment declaration started here
    <!--- end manshet --->
  • Error Line 842, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start top5 --->
  • Info Line 842, Column 1: comment declaration started here
    <!--- start top5 --->
  • Warning Line 846, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51520&Jor=3" title="28/02/2013 ">هیندست…

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

  • Warning Line 846, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51520&Jor=3" title="28/02/2013 ">هیندست…

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

  • Error Line 846, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51520&Jor=3" title="28/02/2013 ">هیندست…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 846, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51520&Jor=3" title="28/02/2013 ">هیندستان: ئه‌نفل…

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

  • Warning Line 846, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51520&Jor=3" title="28/02/2013 ">هیندستان: ئه‌نفل…

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

  • Error Line 846, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51520&Jor=3" title="28/02/2013 ">هیندستان: ئه‌نفل…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 849, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51519&Jor=3" title="28/02/2013 ">ئه‌مری…

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

  • Warning Line 849, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51519&Jor=3" title="28/02/2013 ">ئه‌مری…

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

  • Error Line 849, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51519&Jor=3" title="28/02/2013 ">ئه‌مری…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 849, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51519&Jor=3" title="28/02/2013 ">ئه‌مریكا: 60 ملی…

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

  • Warning Line 849, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51519&Jor=3" title="28/02/2013 ">ئه‌مریكا: 60 ملی…

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

  • Error Line 849, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51519&Jor=3" title="28/02/2013 ">ئه‌مریكا: 60 ملی…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 852, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51518&Jor=1" title="28/02/2013 "> به‌وێ…

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

  • Warning Line 852, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51518&Jor=1" title="28/02/2013 "> به‌وێ…

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

  • Error Line 852, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51518&Jor=1" title="28/02/2013 "> به‌وێ…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 852, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51518&Jor=1" title="28/02/2013 "> به‌وێنه‌،هه‌ولێ…

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

  • Warning Line 852, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51518&Jor=1" title="28/02/2013 "> به‌وێنه‌،هه‌ولێ…

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

  • Error Line 852, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51518&Jor=1" title="28/02/2013 "> به‌وێنه‌،هه‌ولێ…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 854, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51516&Jor=1" title="28/02/2013 ">كۆمه‌ڵ…

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

  • Warning Line 854, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51516&Jor=1" title="28/02/2013 ">كۆمه‌ڵ…

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

  • Error Line 854, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51516&Jor=1" title="28/02/2013 ">كۆمه‌ڵ…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 854, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51516&Jor=1" title="28/02/2013 ">كۆمه‌ڵه‌ی‌ سه‌لا…

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

  • Warning Line 854, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51516&Jor=1" title="28/02/2013 ">كۆمه‌ڵه‌ی‌ سه‌لا…

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

  • Error Line 854, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51516&Jor=1" title="28/02/2013 ">كۆمه‌ڵه‌ی‌ سه‌لا…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 856, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51514&Jor=1" title="28/02/2013 ">حه‌ویج…

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

  • Warning Line 856, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51514&Jor=1" title="28/02/2013 ">حه‌ویج…

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

  • Error Line 856, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51514&Jor=1" title="28/02/2013 ">حه‌ویج…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 856, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51514&Jor=1" title="28/02/2013 ">حه‌ویجه‌: به‌ قه…

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

  • Warning Line 856, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51514&Jor=1" title="28/02/2013 ">حه‌ویجه‌: به‌ قه…

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

  • Error Line 856, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51514&Jor=1" title="28/02/2013 ">حه‌ویجه‌: به‌ قه…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 859, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51513&Jor=1" title="28/02/2013 ">ره‌حما…

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

  • Warning Line 859, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51513&Jor=1" title="28/02/2013 ">ره‌حما…

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

  • Error Line 859, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51513&Jor=1" title="28/02/2013 ">ره‌حما…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 859, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51513&Jor=1" title="28/02/2013 ">ره‌حمان غه‌ریب ب…

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

  • Warning Line 859, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51513&Jor=1" title="28/02/2013 ">ره‌حمان غه‌ریب ب…

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

  • Error Line 859, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51513&Jor=1" title="28/02/2013 ">ره‌حمان غه‌ریب ب…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 861, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51512&Jor=1" title="28/02/2013 ">"هێرشه…

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

  • Warning Line 861, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51512&Jor=1" title="28/02/2013 ">"هێرشه…

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

  • Error Line 861, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51512&Jor=1" title="28/02/2013 ">"هێرشه…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 861, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51512&Jor=1" title="28/02/2013 ">"هێرشه‌كانی‌ دوێ…

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

  • Warning Line 861, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51512&Jor=1" title="28/02/2013 ">"هێرشه‌كانی‌ دوێ…

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

  • Error Line 861, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51512&Jor=1" title="28/02/2013 ">"هێرشه‌كانی‌ دوێ…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 864, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51507&Jor=3" title="28/02/2013 ">داواكا…

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

  • Warning Line 864, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51507&Jor=3" title="28/02/2013 ">داواكا…

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

  • Error Line 864, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51507&Jor=3" title="28/02/2013 ">داواكا…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 864, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51507&Jor=3" title="28/02/2013 ">داواكاری‌ گشتی‌ …

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

  • Warning Line 864, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51507&Jor=3" title="28/02/2013 ">داواكاری‌ گشتی‌ …

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

  • Error Line 864, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51507&Jor=3" title="28/02/2013 ">داواكاری‌ گشتی‌ …

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 866, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51506&Jor=1" title="28/02/2013 ">سه‌رۆك…

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

  • Warning Line 866, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51506&Jor=1" title="28/02/2013 ">سه‌رۆك…

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

  • Error Line 866, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51506&Jor=1" title="28/02/2013 ">سه‌رۆك…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 866, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51506&Jor=1" title="28/02/2013 ">سه‌رۆكی‌ ئه‌نجوم…

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

  • Warning Line 866, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51506&Jor=1" title="28/02/2013 ">سه‌رۆكی‌ ئه‌نجوم…

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

  • Error Line 866, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51506&Jor=1" title="28/02/2013 ">سه‌رۆكی‌ ئه‌نجوم…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 868, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51505&Jor=1" title="28/02/2013 ">دهوك: …

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

  • Warning Line 868, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51505&Jor=1" title="28/02/2013 ">دهوك: …

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

  • Error Line 868, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51505&Jor=1" title="28/02/2013 ">دهوك: …

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 868, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51505&Jor=1" title="28/02/2013 ">دهوك: په‌نابه‌ری…

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

  • Warning Line 868, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51505&Jor=1" title="28/02/2013 ">دهوك: په‌نابه‌ری…

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

  • Error Line 868, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51505&Jor=1" title="28/02/2013 ">دهوك: په‌نابه‌ری…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 870, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51504&Jor=3" title="28/02/2013 ">بڕیاری…

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

  • Warning Line 870, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51504&Jor=3" title="28/02/2013 ">بڕیاری…

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

  • Error Line 870, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51504&Jor=3" title="28/02/2013 ">بڕیاری…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 870, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51504&Jor=3" title="28/02/2013 ">بڕیاری‌ له‌ سێدا…

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

  • Warning Line 870, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51504&Jor=3" title="28/02/2013 ">بڕیاری‌ له‌ سێدا…

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

  • Error Line 870, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51504&Jor=3" title="28/02/2013 ">بڕیاری‌ له‌ سێدا…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 872, Column 137: reference not terminated by REFC delimiter
    …/span><a href="dreja.aspx?=hewal&jmara=51503&Jor=3" title="28/02/2013 ">پاكستا…

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

  • Warning Line 872, Column 137: reference to external entity in attribute value
    …/span><a href="dreja.aspx?=hewal&jmara=51503&Jor=3" title="28/02/2013 ">پاكستا…

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

  • Error Line 872, Column 137: reference to entity "jmara" for which no system identifier could be generated
    …/span><a href="dreja.aspx?=hewal&jmara=51503&Jor=3" title="28/02/2013 ">پاكستا…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 872, Column 147: reference not terminated by REFC delimiter
    …ref="dreja.aspx?=hewal&jmara=51503&Jor=3" title="28/02/2013 ">پاكستان: چوار خو…

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

  • Warning Line 872, Column 147: reference to external entity in attribute value
    …ref="dreja.aspx?=hewal&jmara=51503&Jor=3" title="28/02/2013 ">پاكستان: چوار خو…

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

  • Error Line 872, Column 147: reference to entity "Jor" for which no system identifier could be generated
    …ref="dreja.aspx?=hewal&jmara=51503&Jor=3" title="28/02/2013 ">پاكستان: چوار خو…

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 876, Column 18: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end top5 --->
  • Info Line 876, Column 1: comment declaration started here
    <!--- end top5 --->
  • Error Line 878, Column 26: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start kurdistani --->
  • Info Line 878, Column 1: comment declaration started here
    <!--- start kurdistani --->
  • Warning Line 886, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51499&Jor=1" title="28/02/2013 ">

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

  • Warning Line 886, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51499&Jor=1" title="28/02/2013 ">

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

  • Error Line 886, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51499&Jor=1" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 886, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51499&Jor=1" title="28/02/2013 ">

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

  • Warning Line 886, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51499&Jor=1" title="28/02/2013 ">

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

  • Error Line 886, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51499&Jor=1" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 889, Column 128: reference not terminated by REFC delimiter
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51499&Jor=1">درێژه...‌</a></span>

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

  • Warning Line 889, Column 128: reference to external entity in attribute value
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51499&Jor=1">درێژه...‌</a></span>

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

  • Error Line 889, Column 128: reference to entity "jmara" for which no system identifier could be generated
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51499&Jor=1">درێژه...‌</a></span>

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 889, Column 138: reference not terminated by REFC delimiter
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51499&Jor=1">درێژه...‌</a></span>

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

  • Warning Line 889, Column 138: reference to external entity in attribute value
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51499&Jor=1">درێژه...‌</a></span>

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

  • Error Line 889, Column 138: reference to entity "Jor" for which no system identifier could be generated
    …ss="drejamm"><a href="dreja.aspx?=hewal&jmara=51499&Jor=1">درێژه...‌</a></span>

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 895, Column 24: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end kurdistani --->
  • Info Line 895, Column 1: comment declaration started here
    <!--- end kurdistani --->
  • Error Line 897, Column 24: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start morekurd --->
  • Info Line 897, Column 1: comment declaration started here
    <!--- start morekurd --->
  • Warning Line 900, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51494&Jor=1" title="28/02/2013 ">

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

  • Warning Line 900, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51494&Jor=1" title="28/02/2013 ">

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

  • Error Line 900, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51494&Jor=1" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 900, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51494&Jor=1" title="28/02/2013 ">

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

  • Warning Line 900, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51494&Jor=1" title="28/02/2013 ">

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

  • Error Line 900, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51494&Jor=1" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 904, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51493&Jor=1" title="28/02/2013 ">

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

  • Warning Line 904, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51493&Jor=1" title="28/02/2013 ">

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

  • Error Line 904, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51493&Jor=1" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 904, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51493&Jor=1" title="28/02/2013 ">

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

  • Warning Line 904, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51493&Jor=1" title="28/02/2013 ">

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

  • Error Line 904, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51493&Jor=1" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 908, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51491&Jor=1" title="28/02/2013 ">

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

  • Warning Line 908, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51491&Jor=1" title="28/02/2013 ">

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

  • Error Line 908, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51491&Jor=1" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 908, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51491&Jor=1" title="28/02/2013 ">

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

  • Warning Line 908, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51491&Jor=1" title="28/02/2013 ">

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

  • Error Line 908, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51491&Jor=1" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 912, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51490&Jor=1" title="28/02/2013 ">

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

  • Warning Line 912, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51490&Jor=1" title="28/02/2013 ">

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

  • Error Line 912, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51490&Jor=1" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 912, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51490&Jor=1" title="28/02/2013 ">

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

  • Warning Line 912, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51490&Jor=1" title="28/02/2013 ">

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

  • Error Line 912, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51490&Jor=1" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 916, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51488&Jor=1" title="28/02/2013 ">

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

  • Warning Line 916, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51488&Jor=1" title="28/02/2013 ">

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

  • Error Line 916, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51488&Jor=1" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 916, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51488&Jor=1" title="28/02/2013 ">

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

  • Warning Line 916, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51488&Jor=1" title="28/02/2013 ">

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

  • Error Line 916, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51488&Jor=1" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 920, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51487&Jor=1" title="28/02/2013 ">

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

  • Warning Line 920, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51487&Jor=1" title="28/02/2013 ">

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

  • Error Line 920, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51487&Jor=1" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 920, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51487&Jor=1" title="28/02/2013 ">

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

  • Warning Line 920, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51487&Jor=1" title="28/02/2013 ">

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

  • Error Line 920, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51487&Jor=1" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 924, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51485&Jor=1" title="28/02/2013 ">

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

  • Warning Line 924, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51485&Jor=1" title="28/02/2013 ">

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

  • Error Line 924, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51485&Jor=1" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 924, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51485&Jor=1" title="28/02/2013 ">

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

  • Warning Line 924, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51485&Jor=1" title="28/02/2013 ">

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

  • Error Line 924, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51485&Jor=1" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 928, Column 22: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end morekurd --->
  • Info Line 928, Column 1: comment declaration started here
    <!--- end morekurd --->
  • Error Line 929, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start iraqi --->
  • Info Line 929, Column 1: comment declaration started here
    <!--- start iraqi --->
  • Warning Line 938, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2" title="28/02/2013 ">

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

  • Warning Line 938, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2" title="28/02/2013 ">

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

  • Error Line 938, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 938, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2" title="28/02/2013 ">

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

  • Warning Line 938, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2" title="28/02/2013 ">

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

  • Error Line 938, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 943, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2">

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

  • Warning Line 943, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2">

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

  • Error Line 943, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 943, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2">

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

  • Warning Line 943, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2">

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

  • Error Line 943, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51501&Jor=2">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 950, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end iraqi --->
  • Info Line 950, Column 1: comment declaration started here
    <!--- end iraqi --->
  • Error Line 952, Column 25: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start moreiraqi --->
  • Info Line 952, Column 1: comment declaration started here
    <!--- start moreiraqi --->
  • Warning Line 955, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51500&Jor=2" title="28/02/2013 ">

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

  • Warning Line 955, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51500&Jor=2" title="28/02/2013 ">

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

  • Error Line 955, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51500&Jor=2" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 955, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51500&Jor=2" title="28/02/2013 ">

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

  • Warning Line 955, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51500&Jor=2" title="28/02/2013 ">

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

  • Error Line 955, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51500&Jor=2" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 959, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51497&Jor=2" title="28/02/2013 ">

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

  • Warning Line 959, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51497&Jor=2" title="28/02/2013 ">

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

  • Error Line 959, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51497&Jor=2" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 959, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51497&Jor=2" title="28/02/2013 ">

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

  • Warning Line 959, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51497&Jor=2" title="28/02/2013 ">

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

  • Error Line 959, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51497&Jor=2" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 963, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51496&Jor=2" title="28/02/2013 ">

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

  • Warning Line 963, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51496&Jor=2" title="28/02/2013 ">

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

  • Error Line 963, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51496&Jor=2" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 963, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51496&Jor=2" title="28/02/2013 ">

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

  • Warning Line 963, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51496&Jor=2" title="28/02/2013 ">

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

  • Error Line 963, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51496&Jor=2" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 967, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51492&Jor=2" title="28/02/2013 ">

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

  • Warning Line 967, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51492&Jor=2" title="28/02/2013 ">

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

  • Error Line 967, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51492&Jor=2" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 967, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51492&Jor=2" title="28/02/2013 ">

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

  • Warning Line 967, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51492&Jor=2" title="28/02/2013 ">

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

  • Error Line 967, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51492&Jor=2" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 971, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51489&Jor=2" title="28/02/2013 ">

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

  • Warning Line 971, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51489&Jor=2" title="28/02/2013 ">

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

  • Error Line 971, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51489&Jor=2" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 971, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51489&Jor=2" title="28/02/2013 ">

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

  • Warning Line 971, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51489&Jor=2" title="28/02/2013 ">

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

  • Error Line 971, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51489&Jor=2" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 975, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51486&Jor=2" title="28/02/2013 ">

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

  • Warning Line 975, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51486&Jor=2" title="28/02/2013 ">

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

  • Error Line 975, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51486&Jor=2" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 975, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51486&Jor=2" title="28/02/2013 ">

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

  • Warning Line 975, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51486&Jor=2" title="28/02/2013 ">

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

  • Error Line 975, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51486&Jor=2" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 979, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51479&Jor=2" title="28/02/2013 ">

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

  • Warning Line 979, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51479&Jor=2" title="28/02/2013 ">

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

  • Error Line 979, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51479&Jor=2" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 979, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51479&Jor=2" title="28/02/2013 ">

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

  • Warning Line 979, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51479&Jor=2" title="28/02/2013 ">

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

  • Error Line 979, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51479&Jor=2" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 983, Column 23: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end moreiraqi --->
  • Info Line 983, Column 1: comment declaration started here
    <!--- end moreiraqi --->
  • Error Line 985, Column 22: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start jihani --->
  • Info Line 985, Column 1: comment declaration started here
    <!--- start jihani --->
  • Warning Line 993, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51498&Jor=3" title="28/02/2013 ">

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

  • Warning Line 993, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51498&Jor=3" title="28/02/2013 ">

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

  • Error Line 993, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51498&Jor=3" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 993, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51498&Jor=3" title="28/02/2013 ">

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

  • Warning Line 993, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51498&Jor=3" title="28/02/2013 ">

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

  • Error Line 993, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51498&Jor=3" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 998, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51498&Jor=3">

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

  • Warning Line 998, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51498&Jor=3">

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

  • Error Line 998, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51498&Jor=3">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 998, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51498&Jor=3">

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

  • Warning Line 998, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51498&Jor=3">

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

  • Error Line 998, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51498&Jor=3">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1005, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end jihani --->
  • Info Line 1005, Column 1: comment declaration started here
    <!--- end jihani --->
  • Error Line 1007, Column 26: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start morejihani --->
  • Info Line 1007, Column 1: comment declaration started here
    <!--- start morejihani --->
  • Warning Line 1010, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51484&Jor=3" title="28/02/2013 ">

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

  • Warning Line 1010, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51484&Jor=3" title="28/02/2013 ">

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

  • Error Line 1010, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51484&Jor=3" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1010, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51484&Jor=3" title="28/02/2013 ">

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

  • Warning Line 1010, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51484&Jor=3" title="28/02/2013 ">

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

  • Error Line 1010, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51484&Jor=3" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1014, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51474&Jor=3" title="28/02/2013 ">

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

  • Warning Line 1014, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51474&Jor=3" title="28/02/2013 ">

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

  • Error Line 1014, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51474&Jor=3" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1014, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51474&Jor=3" title="28/02/2013 ">

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

  • Warning Line 1014, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51474&Jor=3" title="28/02/2013 ">

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

  • Error Line 1014, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51474&Jor=3" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1018, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51461&Jor=3" title="27/02/2013 ">

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

  • Warning Line 1018, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51461&Jor=3" title="27/02/2013 ">

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

  • Error Line 1018, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51461&Jor=3" title="27/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1018, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51461&Jor=3" title="27/02/2013 ">

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

  • Warning Line 1018, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51461&Jor=3" title="27/02/2013 ">

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

  • Error Line 1018, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51461&Jor=3" title="27/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1022, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51456&Jor=3" title="27/02/2013 ">

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

  • Warning Line 1022, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51456&Jor=3" title="27/02/2013 ">

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

  • Error Line 1022, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51456&Jor=3" title="27/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1022, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51456&Jor=3" title="27/02/2013 ">

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

  • Warning Line 1022, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51456&Jor=3" title="27/02/2013 ">

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

  • Error Line 1022, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51456&Jor=3" title="27/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1026, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51453&Jor=3" title="27/02/2013 ">

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

  • Warning Line 1026, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51453&Jor=3" title="27/02/2013 ">

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

  • Error Line 1026, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51453&Jor=3" title="27/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1026, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51453&Jor=3" title="27/02/2013 ">

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

  • Warning Line 1026, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51453&Jor=3" title="27/02/2013 ">

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

  • Error Line 1026, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51453&Jor=3" title="27/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1030, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51448&Jor=3" title="27/02/2013 ">

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

  • Warning Line 1030, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51448&Jor=3" title="27/02/2013 ">

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

  • Error Line 1030, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51448&Jor=3" title="27/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1030, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51448&Jor=3" title="27/02/2013 ">

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

  • Warning Line 1030, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51448&Jor=3" title="27/02/2013 ">

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

  • Error Line 1030, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51448&Jor=3" title="27/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1034, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51445&Jor=3" title="27/02/2013 ">

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

  • Warning Line 1034, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51445&Jor=3" title="27/02/2013 ">

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

  • Error Line 1034, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51445&Jor=3" title="27/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1034, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51445&Jor=3" title="27/02/2013 ">

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

  • Warning Line 1034, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51445&Jor=3" title="27/02/2013 ">

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

  • Error Line 1034, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51445&Jor=3" title="27/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1037, Column 24: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end morejihani --->
  • Info Line 1037, Column 1: comment declaration started here
    <!--- end morejihani --->
  • Error Line 1042, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start abury --->
  • Info Line 1042, Column 1: comment declaration started here
    <!--- start abury --->
  • Warning Line 1050, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51478&Jor=7" title="28/02/2013 ">

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

  • Warning Line 1050, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51478&Jor=7" title="28/02/2013 ">

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

  • Error Line 1050, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51478&Jor=7" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1050, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51478&Jor=7" title="28/02/2013 ">

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

  • Warning Line 1050, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51478&Jor=7" title="28/02/2013 ">

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

  • Error Line 1050, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51478&Jor=7" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1055, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51478&Jor=7">

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

  • Warning Line 1055, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51478&Jor=7">

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

  • Error Line 1055, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51478&Jor=7">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1055, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51478&Jor=7">

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

  • Warning Line 1055, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51478&Jor=7">

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

  • Error Line 1055, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51478&Jor=7">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1062, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end abury --->
  • Info Line 1062, Column 1: comment declaration started here
    <!--- end abury --->
  • Error Line 1064, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start abury --->
  • Info Line 1064, Column 1: comment declaration started here
    <!--- start abury --->
  • Warning Line 1067, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51295&Jor=7" title="24/02/2013 ">

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

  • Warning Line 1067, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51295&Jor=7" title="24/02/2013 ">

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

  • Error Line 1067, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51295&Jor=7" title="24/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1067, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51295&Jor=7" title="24/02/2013 ">

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

  • Warning Line 1067, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51295&Jor=7" title="24/02/2013 ">

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

  • Error Line 1067, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51295&Jor=7" title="24/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1071, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51205&Jor=7" title="23/02/2013 ">

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

  • Warning Line 1071, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51205&Jor=7" title="23/02/2013 ">

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

  • Error Line 1071, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51205&Jor=7" title="23/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1071, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51205&Jor=7" title="23/02/2013 ">

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

  • Warning Line 1071, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51205&Jor=7" title="23/02/2013 ">

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

  • Error Line 1071, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51205&Jor=7" title="23/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1075, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51192&Jor=7" title="22/02/2013 ">

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

  • Warning Line 1075, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51192&Jor=7" title="22/02/2013 ">

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

  • Error Line 1075, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51192&Jor=7" title="22/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1075, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51192&Jor=7" title="22/02/2013 ">

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

  • Warning Line 1075, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51192&Jor=7" title="22/02/2013 ">

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

  • Error Line 1075, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51192&Jor=7" title="22/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1079, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51157&Jor=7" title="21/02/2013 ">

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

  • Warning Line 1079, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51157&Jor=7" title="21/02/2013 ">

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

  • Error Line 1079, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51157&Jor=7" title="21/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1079, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51157&Jor=7" title="21/02/2013 ">

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

  • Warning Line 1079, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51157&Jor=7" title="21/02/2013 ">

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

  • Error Line 1079, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51157&Jor=7" title="21/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1083, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51156&Jor=7" title="21/02/2013 ">

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

  • Warning Line 1083, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51156&Jor=7" title="21/02/2013 ">

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

  • Error Line 1083, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51156&Jor=7" title="21/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1083, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51156&Jor=7" title="21/02/2013 ">

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

  • Warning Line 1083, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51156&Jor=7" title="21/02/2013 ">

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

  • Error Line 1083, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51156&Jor=7" title="21/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1087, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51155&Jor=7" title="21/02/2013 ">

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

  • Warning Line 1087, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51155&Jor=7" title="21/02/2013 ">

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

  • Error Line 1087, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51155&Jor=7" title="21/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1087, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51155&Jor=7" title="21/02/2013 ">

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

  • Warning Line 1087, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51155&Jor=7" title="21/02/2013 ">

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

  • Error Line 1087, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51155&Jor=7" title="21/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1092, Column 34: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51132&Jor=7" title="21/02/2013 ">

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

  • Warning Line 1092, Column 34: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51132&Jor=7" title="21/02/2013 ">

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

  • Error Line 1092, Column 34: reference to entity "jmara" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51132&Jor=7" title="21/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1092, Column 44: reference not terminated by REFC delimiter
    	<a href="dreja.aspx?=hewal&jmara=51132&Jor=7" title="21/02/2013 ">

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

  • Warning Line 1092, Column 44: reference to external entity in attribute value
    	<a href="dreja.aspx?=hewal&jmara=51132&Jor=7" title="21/02/2013 ">

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

  • Error Line 1092, Column 44: reference to entity "Jor" for which no system identifier could be generated
    	<a href="dreja.aspx?=hewal&jmara=51132&Jor=7" title="21/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1095, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end abury --->
  • Info Line 1095, Column 1: comment declaration started here
    <!--- end abury --->
  • Error Line 1112, Column 22: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start warzsh --->
  • Info Line 1112, Column 1: comment declaration started here
    <!--- start warzsh --->
  • Warning Line 1120, Column 40: reference not terminated by REFC delimiter
    	<a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16" title="28/02/2013 ">

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

  • Warning Line 1120, Column 40: reference to external entity in attribute value
    	<a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16" title="28/02/2013 ">

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

  • Error Line 1120, Column 40: reference to entity "jmara" for which no system identifier could be generated
    	<a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1120, Column 50: reference not terminated by REFC delimiter
    	<a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16" title="28/02/2013 ">

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

  • Warning Line 1120, Column 50: reference to external entity in attribute value
    	<a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16" title="28/02/2013 ">

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

  • Error Line 1120, Column 50: reference to entity "Jor" for which no system identifier could be generated
    	<a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1125, Column 39: reference not terminated by REFC delimiter
    <a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16">

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

  • Warning Line 1125, Column 39: reference to external entity in attribute value
    <a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16">

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

  • Error Line 1125, Column 39: reference to entity "jmara" for which no system identifier could be generated
    <a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1125, Column 49: reference not terminated by REFC delimiter
    <a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16">

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

  • Warning Line 1125, Column 49: reference to external entity in attribute value
    <a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16">

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

  • Error Line 1125, Column 49: reference to entity "Jor" for which no system identifier could be generated
    <a href="sport/dreja.aspx?=hewal&jmara=15355&Jor=16">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1132, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end warzsh --->
  • Info Line 1132, Column 1: comment declaration started here
    <!--- end warzsh --->
  • Error Line 1134, Column 27: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start morewarzsh  --->
  • Info Line 1134, Column 1: comment declaration started here
    <!--- start morewarzsh  --->
  • Warning Line 1137, Column 40: reference not terminated by REFC delimiter
    	<a href="sport/dreja.aspx?=hewal&jmara=15354&Jor=16" title="28/02/2013 ">

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

  • Warning Line 1137, Column 40: reference to external entity in attribute value
    	<a href="sport/dreja.aspx?=hewal&jmara=15354&Jor=16" title="28/02/2013 ">

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

  • Error Line 1137, Column 40: reference to entity "jmara" for which no system identifier could be generated
    	<a href="sport/dreja.aspx?=hewal&jmara=15354&Jor=16" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1137, Column 50: reference not terminated by REFC delimiter
    	<a href="sport/dreja.aspx?=hewal&jmara=15354&Jor=16" title="28/02/2013 ">

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

  • Warning Line 1137, Column 50: reference to external entity in attribute value
    	<a href="sport/dreja.aspx?=hewal&jmara=15354&Jor=16" title="28/02/2013 ">

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

  • Error Line 1137, Column 50: reference to entity "Jor" for which no system identifier could be generated
    	<a href="sport/dreja.aspx?=hewal&jmara=15354&Jor=16" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1141, Column 40: reference not terminated by REFC delimiter
    	<a href="sport/dreja.aspx?=hewal&jmara=15353&Jor=16" title="28/02/2013 ">

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

  • Warning Line 1141, Column 40: reference to external entity in attribute value
    	<a href="sport/dreja.aspx?=hewal&jmara=15353&Jor=16" title="28/02/2013 ">

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

  • Error Line 1141, Column 40: reference to entity "jmara" for which no system identifier could be generated
    	<a href="sport/dreja.aspx?=hewal&jmara=15353&Jor=16" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1141, Column 50: reference not terminated by REFC delimiter
    	<a href="sport/dreja.aspx?=hewal&jmara=15353&Jor=16" title="28/02/2013 ">

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

  • Warning Line 1141, Column 50: reference to external entity in attribute value
    	<a href="sport/dreja.aspx?=hewal&jmara=15353&Jor=16" title="28/02/2013 ">

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

  • Error Line 1141, Column 50: reference to entity "Jor" for which no system identifier could be generated
    	<a href="sport/dreja.aspx?=hewal&jmara=15353&Jor=16" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1145, Column 40: reference not terminated by REFC delimiter
    	<a href="sport/dreja.aspx?=hewal&jmara=15352&Jor=16" title="28/02/2013 ">

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

  • Warning Line 1145, Column 40: reference to external entity in attribute value
    	<a href="sport/dreja.aspx?=hewal&jmara=15352&Jor=16" title="28/02/2013 ">

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

  • Error Line 1145, Column 40: reference to entity "jmara" for which no system identifier could be generated
    	<a href="sport/dreja.aspx?=hewal&jmara=15352&Jor=16" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1145, Column 50: reference not terminated by REFC delimiter
    	<a href="sport/dreja.aspx?=hewal&jmara=15352&Jor=16" title="28/02/2013 ">

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

  • Warning Line 1145, Column 50: reference to external entity in attribute value
    	<a href="sport/dreja.aspx?=hewal&jmara=15352&Jor=16" title="28/02/2013 ">

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

  • Error Line 1145, Column 50: reference to entity "Jor" for which no system identifier could be generated
    	<a href="sport/dreja.aspx?=hewal&jmara=15352&Jor=16" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1149, Column 40: reference not terminated by REFC delimiter
    	<a href="sport/dreja.aspx?=hewal&jmara=15351&Jor=16" title="28/02/2013 ">

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

  • Warning Line 1149, Column 40: reference to external entity in attribute value
    	<a href="sport/dreja.aspx?=hewal&jmara=15351&Jor=16" title="28/02/2013 ">

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

  • Error Line 1149, Column 40: reference to entity "jmara" for which no system identifier could be generated
    	<a href="sport/dreja.aspx?=hewal&jmara=15351&Jor=16" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1149, Column 50: reference not terminated by REFC delimiter
    	<a href="sport/dreja.aspx?=hewal&jmara=15351&Jor=16" title="28/02/2013 ">

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

  • Warning Line 1149, Column 50: reference to external entity in attribute value
    	<a href="sport/dreja.aspx?=hewal&jmara=15351&Jor=16" title="28/02/2013 ">

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

  • Error Line 1149, Column 50: reference to entity "Jor" for which no system identifier could be generated
    	<a href="sport/dreja.aspx?=hewal&jmara=15351&Jor=16" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1152, Column 24: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end morewarzsh --->
  • Info Line 1152, Column 1: comment declaration started here
    <!--- end morewarzsh --->
  • Error Line 1162, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- Start left --->
  • Info Line 1162, Column 1: comment declaration started here
    <!--- Start left --->
  • Error Line 1164, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start gosha --->
  • Info Line 1164, Column 1: comment declaration started here
    <!--- start gosha --->
  • Error Line 1167, Column 30: invalid comment declaration: found name character outside comment but inside comment declaration
            <!--- start hewal2 --->
  • Info Line 1167, Column 9: comment declaration started here
            <!--- start hewal2 --->
  • Error Line 1169, Column 28: invalid comment declaration: found name character outside comment but inside comment declaration
            <!--- end hewal2 --->
  • Info Line 1169, Column 9: comment declaration started here
            <!--- end hewal2 --->
  • Error Line 1173, Column 36: invalid comment declaration: found name character outside comment but inside comment declaration
            	<!--- start asia reklam --->
  • Info Line 1173, Column 10: comment declaration started here
            	<!--- start asia reklam --->
  • Error Line 1181, Column 29: invalid comment declaration: found name character outside comment but inside comment declaration
            	<!--- start wtar --->
  • Info Line 1181, Column 10: comment declaration started here
            	<!--- start wtar --->
  • Warning Line 1199, Column 37: cannot generate system identifier for general entity "Jmara"
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">

    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 1199, Column 37: general entity "Jmara" not defined and no default entity
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">

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

  • Warning Line 1199, Column 42: reference not terminated by REFC delimiter
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">

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

  • Warning Line 1199, Column 42: reference to external entity in attribute value
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">

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

  • Error Line 1199, Column 42: reference to entity "Jmara" for which no system identifier could be generated
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">

    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 1199, Column 36: entity was defined here
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">
  • Warning Line 1211, Column 42: reference not terminated by REFC delimiter
    <a href="drejaWtar.aspx?NusarID=197&Jmara=4815">

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

  • Warning Line 1211, Column 42: reference to external entity in attribute value
    <a href="drejaWtar.aspx?NusarID=197&Jmara=4815">

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

  • Error Line 1211, Column 42: reference to entity "Jmara" for which no system identifier could be generated
    <a href="drejaWtar.aspx?NusarID=197&Jmara=4815">

    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 1199, Column 36: entity was defined here
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">
  • Warning Line 1227, Column 41: reference not terminated by REFC delimiter
    <a href="drejaWtar.aspx?NusarID=98&Jmara=4814">

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

  • Warning Line 1227, Column 41: reference to external entity in attribute value
    <a href="drejaWtar.aspx?NusarID=98&Jmara=4814">

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

  • Error Line 1227, Column 41: reference to entity "Jmara" for which no system identifier could be generated
    <a href="drejaWtar.aspx?NusarID=98&Jmara=4814">

    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 1199, Column 36: entity was defined here
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">
  • Warning Line 1240, Column 42: reference not terminated by REFC delimiter
    <a href="drejaWtar.aspx?NusarID=894&Jmara=4813">

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

  • Warning Line 1240, Column 42: reference to external entity in attribute value
    <a href="drejaWtar.aspx?NusarID=894&Jmara=4813">

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

  • Error Line 1240, Column 42: reference to entity "Jmara" for which no system identifier could be generated
    <a href="drejaWtar.aspx?NusarID=894&Jmara=4813">

    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 1199, Column 36: entity was defined here
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">
  • Warning Line 1256, Column 42: reference not terminated by REFC delimiter
    <a href="drejaWtar.aspx?NusarID=893&Jmara=4812">

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

  • Warning Line 1256, Column 42: reference to external entity in attribute value
    <a href="drejaWtar.aspx?NusarID=893&Jmara=4812">

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

  • Error Line 1256, Column 42: reference to entity "Jmara" for which no system identifier could be generated
    <a href="drejaWtar.aspx?NusarID=893&Jmara=4812">

    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 1199, Column 36: entity was defined here
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">
  • Warning Line 1268, Column 42: reference not terminated by REFC delimiter
    <a href="drejaWtar.aspx?NusarID=521&Jmara=4811">

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

  • Warning Line 1268, Column 42: reference to external entity in attribute value
    <a href="drejaWtar.aspx?NusarID=521&Jmara=4811">

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

  • Error Line 1268, Column 42: reference to entity "Jmara" for which no system identifier could be generated
    <a href="drejaWtar.aspx?NusarID=521&Jmara=4811">

    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 1199, Column 36: entity was defined here
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">
  • Warning Line 1285, Column 40: reference not terminated by REFC delimiter
    <a href="drejaWtar.aspx?NusarID=8&Jmara=4810">

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

  • Warning Line 1285, Column 40: reference to external entity in attribute value
    <a href="drejaWtar.aspx?NusarID=8&Jmara=4810">

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

  • Error Line 1285, Column 40: reference to entity "Jmara" for which no system identifier could be generated
    <a href="drejaWtar.aspx?NusarID=8&Jmara=4810">

    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 1199, Column 36: entity was defined here
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">
  • Warning Line 1297, Column 42: reference not terminated by REFC delimiter
    <a href="drejaWtar.aspx?NusarID=311&Jmara=4809">

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

  • Warning Line 1297, Column 42: reference to external entity in attribute value
    <a href="drejaWtar.aspx?NusarID=311&Jmara=4809">

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

  • Error Line 1297, Column 42: reference to entity "Jmara" for which no system identifier could be generated
    <a href="drejaWtar.aspx?NusarID=311&Jmara=4809">

    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 1199, Column 36: entity was defined here
    <a href="drejaWtar.aspx?NusarID=895&Jmara=4816">
  • Error Line 1321, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    	<!--- end wtar --->
  • Info Line 1321, Column 2: comment declaration started here
    	<!--- end wtar --->
  • Error Line 1327, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start video --->
  • Info Line 1327, Column 1: comment declaration started here
    <!--- start video --->
  • Error Line 1328, Column 28: invalid comment declaration: found name character outside comment but inside comment declaration
           <!--- start raport--->
  • Info Line 1328, Column 8: comment declaration started here
           <!--- start raport--->
  • Warning Line 1342, Column 34: reference not terminated by REFC delimiter
    <a href="dreja3.aspx?=hewal&jmara=51333&Jor=5">

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

  • Warning Line 1342, Column 34: reference to external entity in attribute value
    <a href="dreja3.aspx?=hewal&jmara=51333&Jor=5">

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

  • Error Line 1342, Column 34: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja3.aspx?=hewal&jmara=51333&Jor=5">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1342, Column 44: reference not terminated by REFC delimiter
    <a href="dreja3.aspx?=hewal&jmara=51333&Jor=5">

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

  • Warning Line 1342, Column 44: reference to external entity in attribute value
    <a href="dreja3.aspx?=hewal&jmara=51333&Jor=5">

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

  • Error Line 1342, Column 44: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja3.aspx?=hewal&jmara=51333&Jor=5">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1355, Column 15: there is no attribute "type"
      <embed type="application/x-shockwave-flash"

    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 1356, Column 16: there is no attribute "pluginspage"
       pluginspage="http://www.macromedia.com/go/getflashplayer"

    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 1357, Column 10: there is no attribute "width"
       width="320" height="250"

    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 1357, Column 23: there is no attribute "height"
       width="320" height="250"

    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 1358, Column 9: there is no attribute "name"
       name="ramadankurdi" src="reklam/qaiwan2.swf"

    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 1358, Column 28: there is no attribute "src"
       name="ramadankurdi" src="reklam/qaiwan2.swf"

    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 1359, Column 12: there is no attribute "bgcolor"
       bgcolor="#ffffff" quality="high"

    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 1359, Column 30: there is no attribute "quality"
       bgcolor="#ffffff" quality="high"

    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 1360, Column 18: there is no attribute "swLiveConnect"
       swLiveConnect="true" allowScriptAccess="samedomain"

    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 1360, Column 43: there is no attribute "allowScriptAccess"
       swLiveConnect="true" allowScriptAccess="samedomain"

    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 1361, Column 3: element "embed" undefined
      ></embed>

    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 1367, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end raport--->
  • Info Line 1367, Column 1: comment declaration started here
    <!--- end raport--->
  • Error Line 1370, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end video --->
  • Info Line 1370, Column 1: comment declaration started here
    <!--- end video --->
  • Error Line 1376, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start blaw--->
  • Info Line 1376, Column 1: comment declaration started here
    <!--- start blaw--->
  • Error Line 1379, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start video --->
  • Info Line 1379, Column 1: comment declaration started here
    <!--- start video --->
  • Warning Line 1393, Column 33: reference not terminated by REFC delimiter
    <a href="Video.aspx?=hewal&jmara=717">

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

  • Warning Line 1393, Column 33: reference to external entity in attribute value
    <a href="Video.aspx?=hewal&jmara=717">

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

  • Error Line 1393, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="Video.aspx?=hewal&jmara=717">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1417, Column 33: reference not terminated by REFC delimiter
    <a href="Video.aspx?=hewal&jmara=716">

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

  • Warning Line 1417, Column 33: reference to external entity in attribute value
    <a href="Video.aspx?=hewal&jmara=716">

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

  • Error Line 1417, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="Video.aspx?=hewal&jmara=716">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1441, Column 33: reference not terminated by REFC delimiter
    <a href="Video.aspx?=hewal&jmara=715">

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

  • Warning Line 1441, Column 33: reference to external entity in attribute value
    <a href="Video.aspx?=hewal&jmara=715">

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

  • Error Line 1441, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="Video.aspx?=hewal&jmara=715">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1465, Column 33: reference not terminated by REFC delimiter
    <a href="Video.aspx?=hewal&jmara=714">

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

  • Warning Line 1465, Column 33: reference to external entity in attribute value
    <a href="Video.aspx?=hewal&jmara=714">

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

  • Error Line 1465, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="Video.aspx?=hewal&jmara=714">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1489, Column 33: reference not terminated by REFC delimiter
    <a href="Video.aspx?=hewal&jmara=713">

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

  • Warning Line 1489, Column 33: reference to external entity in attribute value
    <a href="Video.aspx?=hewal&jmara=713">

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

  • Error Line 1489, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="Video.aspx?=hewal&jmara=713">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1512, Column 34: reference not terminated by REFC delimiter
     <a href="Video.aspx?=hewal&jmara=717" class="toc someclass"><img src="videoiam…

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

  • Warning Line 1512, Column 34: reference to external entity in attribute value
     <a href="Video.aspx?=hewal&jmara=717" class="toc someclass"><img src="videoiam…

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

  • Error Line 1512, Column 34: reference to entity "jmara" for which no system identifier could be generated
     <a href="Video.aspx?=hewal&jmara=717" class="toc someclass"><img src="videoiam…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Error Line 1512, Column 341: required attribute "alt" not specified
    …                                                                      " /></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>.

  • Warning Line 1514, Column 34: reference not terminated by REFC delimiter
     <a href="Video.aspx?=hewal&jmara=716" class="toc someclass"><img src="videoiam…

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

  • Warning Line 1514, Column 34: reference to external entity in attribute value
     <a href="Video.aspx?=hewal&jmara=716" class="toc someclass"><img src="videoiam…

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

  • Error Line 1514, Column 34: reference to entity "jmara" for which no system identifier could be generated
     <a href="Video.aspx?=hewal&jmara=716" class="toc someclass"><img src="videoiam…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Error Line 1514, Column 341: required attribute "alt" not specified
    …                                                                      " /></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>.

  • Warning Line 1516, Column 34: reference not terminated by REFC delimiter
     <a href="Video.aspx?=hewal&jmara=715" class="toc someclass"><img src="videoiam…

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

  • Warning Line 1516, Column 34: reference to external entity in attribute value
     <a href="Video.aspx?=hewal&jmara=715" class="toc someclass"><img src="videoiam…

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

  • Error Line 1516, Column 34: reference to entity "jmara" for which no system identifier could be generated
     <a href="Video.aspx?=hewal&jmara=715" class="toc someclass"><img src="videoiam…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Error Line 1516, Column 341: required attribute "alt" not specified
    …                                                                      " /></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>.

  • Warning Line 1518, Column 34: reference not terminated by REFC delimiter
     <a href="Video.aspx?=hewal&jmara=714" class="toc someclass"><img src="videoiam…

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

  • Warning Line 1518, Column 34: reference to external entity in attribute value
     <a href="Video.aspx?=hewal&jmara=714" class="toc someclass"><img src="videoiam…

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

  • Error Line 1518, Column 34: reference to entity "jmara" for which no system identifier could be generated
     <a href="Video.aspx?=hewal&jmara=714" class="toc someclass"><img src="videoiam…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Error Line 1518, Column 341: required attribute "alt" not specified
    …                                                                      " /></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>.

  • Warning Line 1520, Column 34: reference not terminated by REFC delimiter
     <a href="Video.aspx?=hewal&jmara=713" class="toc someclass"><img src="videoiam…

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

  • Warning Line 1520, Column 34: reference to external entity in attribute value
     <a href="Video.aspx?=hewal&jmara=713" class="toc someclass"><img src="videoiam…

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

  • Error Line 1520, Column 34: reference to entity "jmara" for which no system identifier could be generated
     <a href="Video.aspx?=hewal&jmara=713" class="toc someclass"><img src="videoiam…

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Error Line 1520, Column 341: required attribute "alt" not specified
    …                                                                      " /></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 1543, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end video --->
  • Info Line 1543, Column 1: comment declaration started here
    <!--- end video --->
  • Error Line 1561, Column 3: element "embed" undefined
      ></embed>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1575, Column 34: reference not terminated by REFC delimiter
    <a href="dreja2.aspx?=hewal&jmara=51441&Jor=4">

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

  • Warning Line 1575, Column 34: reference to external entity in attribute value
    <a href="dreja2.aspx?=hewal&jmara=51441&Jor=4">

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

  • Error Line 1575, Column 34: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja2.aspx?=hewal&jmara=51441&Jor=4">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1575, Column 44: reference not terminated by REFC delimiter
    <a href="dreja2.aspx?=hewal&jmara=51441&Jor=4">

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

  • Warning Line 1575, Column 44: reference to external entity in attribute value
    <a href="dreja2.aspx?=hewal&jmara=51441&Jor=4">

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

  • Error Line 1575, Column 44: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja2.aspx?=hewal&jmara=51441&Jor=4">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1588, Column 50: required attribute "alt" not specified
    <img  height="115" src="xarama.png" width="350" /></a></div>

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

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

  • Error Line 1595, Column 43: required attribute "alt" not specified
    <img src="reklam/shanor4.png"  border="0"/></a>

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

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

  • Error Line 1611, Column 17: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end blaw--->
  • Info Line 1611, Column 1: comment declaration started here
    <!--- end blaw--->
  • Error Line 1614, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end gosha --->
  • Info Line 1614, Column 1: comment declaration started here
    <!--- end gosha --->
  • Error Line 1616, Column 22: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start reklam --->
  • Info Line 1616, Column 1: comment declaration started here
    <!--- start reklam --->
  • Error Line 1619, Column 90: required attribute "alt" not specified
    …n"><a href="hewal5.aspx?Jor=18"><img src="n3d6zgzi.jpg" border="0" /></a></div>

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

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

  • Warning Line 1623, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51495&Jor=18">

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

  • Warning Line 1623, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51495&Jor=18">

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

  • Error Line 1623, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51495&Jor=18">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1623, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51495&Jor=18">

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

  • Warning Line 1623, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51495&Jor=18">

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

  • Error Line 1623, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51495&Jor=18">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1628, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51483&Jor=18">

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

  • Warning Line 1628, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51483&Jor=18">

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

  • Error Line 1628, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51483&Jor=18">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1628, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51483&Jor=18">

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

  • Warning Line 1628, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51483&Jor=18">

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

  • Error Line 1628, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51483&Jor=18">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1633, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51464&Jor=18">

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

  • Warning Line 1633, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51464&Jor=18">

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

  • Error Line 1633, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51464&Jor=18">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1633, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51464&Jor=18">

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

  • Warning Line 1633, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51464&Jor=18">

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

  • Error Line 1633, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51464&Jor=18">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1644, Column 93: required attribute "alt" not specified
    …<a href="hewal5.aspx?Jor=47"><img src="images/XAN1.png" border="0" /></a></div>

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

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

  • Warning Line 1648, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51502&Jor=47">

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

  • Warning Line 1648, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51502&Jor=47">

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

  • Error Line 1648, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51502&Jor=47">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1648, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51502&Jor=47">

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

  • Warning Line 1648, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51502&Jor=47">

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

  • Error Line 1648, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51502&Jor=47">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1653, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51359&Jor=47">

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

  • Warning Line 1653, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51359&Jor=47">

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

  • Error Line 1653, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51359&Jor=47">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1653, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51359&Jor=47">

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

  • Warning Line 1653, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51359&Jor=47">

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

  • Error Line 1653, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51359&Jor=47">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1658, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51357&Jor=47">

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

  • Warning Line 1658, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51357&Jor=47">

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

  • Error Line 1658, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51357&Jor=47">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1658, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51357&Jor=47">

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

  • Warning Line 1658, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51357&Jor=47">

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

  • Error Line 1658, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51357&Jor=47">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1663, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51218&Jor=47">

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

  • Warning Line 1663, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51218&Jor=47">

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

  • Error Line 1663, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51218&Jor=47">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1663, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51218&Jor=47">

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

  • Warning Line 1663, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51218&Jor=47">

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

  • Error Line 1663, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51218&Jor=47">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1671, Column 92: required attribute "alt" not specified
    …><a href="hewal5.aspx?Jor=19"><img src="n3d6zgziww.jpg" border="0" /></a></div>

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

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

  • Warning Line 1675, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51420&Jor=19">

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

  • Warning Line 1675, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51420&Jor=19">

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

  • Error Line 1675, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51420&Jor=19">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1675, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51420&Jor=19">

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

  • Warning Line 1675, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51420&Jor=19">

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

  • Error Line 1675, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51420&Jor=19">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1680, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51398&Jor=19">

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

  • Warning Line 1680, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51398&Jor=19">

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

  • Error Line 1680, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51398&Jor=19">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1680, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51398&Jor=19">

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

  • Warning Line 1680, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51398&Jor=19">

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

  • Error Line 1680, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51398&Jor=19">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1685, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51334&Jor=19">

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

  • Warning Line 1685, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51334&Jor=19">

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

  • Error Line 1685, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51334&Jor=19">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1685, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51334&Jor=19">

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

  • Warning Line 1685, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51334&Jor=19">

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

  • Error Line 1685, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51334&Jor=19">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1694, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end reklam --->
  • Info Line 1694, Column 1: comment declaration started here
    <!--- end reklam --->
  • Error Line 1695, Column 18: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- End left --->
  • Info Line 1695, Column 1: comment declaration started here
    <!--- End left --->
  • Error Line 1699, Column 18: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end main --->
  • Info Line 1699, Column 1: comment declaration started here
    <!--- end main --->
  • Error Line 1700, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start video --->
  • Info Line 1700, Column 1: comment declaration started here
    <!--- start video --->
  • Error Line 1704, Column 16: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- REKLAM --->
  • Info Line 1704, Column 1: comment declaration started here
    <!--- REKLAM --->
  • Error Line 1708, Column 16: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- REKLAM --->
  • Info Line 1708, Column 1: comment declaration started here
    <!--- REKLAM --->
  • Error Line 1711, 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 1713, 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 1715, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end video --->
  • Info Line 1715, Column 1: comment declaration started here
    <!--- end video --->
  • Error Line 1718, Column 25: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start photonews --->
  • Info Line 1718, Column 1: comment declaration started here
    <!--- start photonews --->
  • Error Line 1721, Column 68: required attribute "alt" not specified
    <div style="float:right;width:30px"><img src="images/gallery.png" /></div>

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

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

  • Error Line 1726, Column 29: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start contenr video --->
  • Info Line 1726, Column 1: comment declaration started here
    <!--- start contenr video --->
  • Error Line 1734, Column 64: required attribute "alt" not specified
    <img src="imgnews/national_geographic_photo_c.jpg" 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 1746, Column 68: required attribute "alt" not specified
    <img src="imgnews/Only-in-Russia-part3-042622013s.png" border="0" /></a>

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

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

  • Error Line 1758, Column 71: required attribute "alt" not specified
    <img src="imgnews/world-best-dressed-dog-12622013sss.png" border="0" /></a>

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

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

  • Error Line 1772, Column 27: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end contenr video --->
  • Info Line 1772, Column 1: comment declaration started here
    <!--- end contenr video --->
  • Error Line 1781, Column 23: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end photonews --->
  • Info Line 1781, Column 1: comment declaration started here
    <!--- end photonews --->
  • Error Line 1782, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start other --->
  • Info Line 1782, Column 1: comment declaration started here
    <!--- start other --->
  • Error Line 1790, Column 63: required attribute "alt" not specified
    <div class="hamaranghead"><img src="images/hamarangline.png" /></div>

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

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

  • Warning Line 1793, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51509&Jor=8" title="28/02/2013 ">

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

  • Warning Line 1793, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51509&Jor=8" title="28/02/2013 ">

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

  • Error Line 1793, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51509&Jor=8" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1793, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51509&Jor=8" title="28/02/2013 ">

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

  • Warning Line 1793, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51509&Jor=8" title="28/02/2013 ">

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

  • Error Line 1793, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51509&Jor=8" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1798, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51477&Jor=8" title="28/02/2013 ">

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

  • Warning Line 1798, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51477&Jor=8" title="28/02/2013 ">

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

  • Error Line 1798, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51477&Jor=8" title="28/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1798, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51477&Jor=8" title="28/02/2013 ">

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

  • Warning Line 1798, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51477&Jor=8" title="28/02/2013 ">

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

  • Error Line 1798, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51477&Jor=8" title="28/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1802, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51427&Jor=8" title="27/02/2013 ">

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

  • Warning Line 1802, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51427&Jor=8" title="27/02/2013 ">

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

  • Error Line 1802, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51427&Jor=8" title="27/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1802, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51427&Jor=8" title="27/02/2013 ">

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

  • Warning Line 1802, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51427&Jor=8" title="27/02/2013 ">

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

  • Error Line 1802, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51427&Jor=8" title="27/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1806, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51410&Jor=8" title="26/02/2013 ">

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

  • Warning Line 1806, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51410&Jor=8" title="26/02/2013 ">

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

  • Error Line 1806, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51410&Jor=8" title="26/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1806, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51410&Jor=8" title="26/02/2013 ">

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

  • Warning Line 1806, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51410&Jor=8" title="26/02/2013 ">

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

  • Error Line 1806, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51410&Jor=8" title="26/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1810, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51389&Jor=8" title="26/02/2013 ">

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

  • Warning Line 1810, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51389&Jor=8" title="26/02/2013 ">

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

  • Error Line 1810, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51389&Jor=8" title="26/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1810, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51389&Jor=8" title="26/02/2013 ">

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

  • Warning Line 1810, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51389&Jor=8" title="26/02/2013 ">

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

  • Error Line 1810, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51389&Jor=8" title="26/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1814, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51368&Jor=8" title="26/02/2013 ">

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

  • Warning Line 1814, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51368&Jor=8" title="26/02/2013 ">

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

  • Error Line 1814, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51368&Jor=8" title="26/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1814, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51368&Jor=8" title="26/02/2013 ">

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

  • Warning Line 1814, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51368&Jor=8" title="26/02/2013 ">

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

  • Error Line 1814, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51368&Jor=8" title="26/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1819, Column 51: reference not terminated by REFC delimiter
    … href="http://xendan.org/dreja.aspx?=hewal&jmara=44445&Jor=44" target="_blank">

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

  • Warning Line 1819, Column 51: reference to external entity in attribute value
    … href="http://xendan.org/dreja.aspx?=hewal&jmara=44445&Jor=44" target="_blank">

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

  • Error Line 1819, Column 51: reference to entity "jmara" for which no system identifier could be generated
    … href="http://xendan.org/dreja.aspx?=hewal&jmara=44445&Jor=44" target="_blank">

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

  • Info Line 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1819, Column 61: reference not terminated by REFC delimiter
    … href="http://xendan.org/dreja.aspx?=hewal&jmara=44445&Jor=44" target="_blank">

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

  • Warning Line 1819, Column 61: reference to external entity in attribute value
    … href="http://xendan.org/dreja.aspx?=hewal&jmara=44445&Jor=44" target="_blank">

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

  • Error Line 1819, Column 61: reference to entity "Jor" for which no system identifier could be generated
    … href="http://xendan.org/dreja.aspx?=hewal&jmara=44445&Jor=44" target="_blank">

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

  • Info Line 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1829, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51444&Jor=14" title="27/02/2013 ">

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

  • Warning Line 1829, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51444&Jor=14" title="27/02/2013 ">

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

  • Error Line 1829, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51444&Jor=14" title="27/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1829, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51444&Jor=14" title="27/02/2013 ">

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

  • Warning Line 1829, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51444&Jor=14" title="27/02/2013 ">

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

  • Error Line 1829, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51444&Jor=14" title="27/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1833, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51421&Jor=14" title="27/02/2013 ">

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

  • Warning Line 1833, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51421&Jor=14" title="27/02/2013 ">

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

  • Error Line 1833, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51421&Jor=14" title="27/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1833, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51421&Jor=14" title="27/02/2013 ">

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

  • Warning Line 1833, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51421&Jor=14" title="27/02/2013 ">

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

  • Error Line 1833, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51421&Jor=14" title="27/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1837, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51393&Jor=14" title="26/02/2013 ">

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

  • Warning Line 1837, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51393&Jor=14" title="26/02/2013 ">

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

  • Error Line 1837, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51393&Jor=14" title="26/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1837, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51393&Jor=14" title="26/02/2013 ">

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

  • Warning Line 1837, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51393&Jor=14" title="26/02/2013 ">

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

  • Error Line 1837, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51393&Jor=14" title="26/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1841, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51366&Jor=14" title="26/02/2013 ">

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

  • Warning Line 1841, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51366&Jor=14" title="26/02/2013 ">

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

  • Error Line 1841, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51366&Jor=14" title="26/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1841, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51366&Jor=14" title="26/02/2013 ">

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

  • Warning Line 1841, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51366&Jor=14" title="26/02/2013 ">

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

  • Error Line 1841, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51366&Jor=14" title="26/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1845, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51284&Jor=14" title="24/02/2013 ">

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

  • Warning Line 1845, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51284&Jor=14" title="24/02/2013 ">

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

  • Error Line 1845, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51284&Jor=14" title="24/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1845, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51284&Jor=14" title="24/02/2013 ">

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

  • Warning Line 1845, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51284&Jor=14" title="24/02/2013 ">

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

  • Error Line 1845, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51284&Jor=14" title="24/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1849, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51253&Jor=14" title="24/02/2013 ">

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

  • Warning Line 1849, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51253&Jor=14" title="24/02/2013 ">

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

  • Error Line 1849, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51253&Jor=14" title="24/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1849, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51253&Jor=14" title="24/02/2013 ">

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

  • Warning Line 1849, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51253&Jor=14" title="24/02/2013 ">

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

  • Error Line 1849, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51253&Jor=14" title="24/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1853, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51181&Jor=14" title="22/02/2013 ">

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

  • Warning Line 1853, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51181&Jor=14" title="22/02/2013 ">

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

  • Error Line 1853, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51181&Jor=14" title="22/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1853, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51181&Jor=14" title="22/02/2013 ">

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

  • Warning Line 1853, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51181&Jor=14" title="22/02/2013 ">

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

  • Error Line 1853, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51181&Jor=14" title="22/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1857, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51077&Jor=14" title="20/02/2013 ">

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

  • Warning Line 1857, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51077&Jor=14" title="20/02/2013 ">

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

  • Error Line 1857, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51077&Jor=14" title="20/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1857, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51077&Jor=14" title="20/02/2013 ">

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

  • Warning Line 1857, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51077&Jor=14" title="20/02/2013 ">

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

  • Error Line 1857, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51077&Jor=14" title="20/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1861, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51037&Jor=14" title="19/02/2013 ">

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

  • Warning Line 1861, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51037&Jor=14" title="19/02/2013 ">

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

  • Error Line 1861, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51037&Jor=14" title="19/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1861, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=51037&Jor=14" title="19/02/2013 ">

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

  • Warning Line 1861, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=51037&Jor=14" title="19/02/2013 ">

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

  • Error Line 1861, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=51037&Jor=14" title="19/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Warning Line 1865, Column 33: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=50952&Jor=14" title="18/02/2013 ">

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

  • Warning Line 1865, Column 33: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=50952&Jor=14" title="18/02/2013 ">

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

  • Error Line 1865, Column 33: reference to entity "jmara" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=50952&Jor=14" title="18/02/2013 ">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1865, Column 43: reference not terminated by REFC delimiter
    <a href="dreja.aspx?=hewal&jmara=50952&Jor=14" title="18/02/2013 ">

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

  • Warning Line 1865, Column 43: reference to external entity in attribute value
    <a href="dreja.aspx?=hewal&jmara=50952&Jor=14" title="18/02/2013 ">

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

  • Error Line 1865, Column 43: reference to entity "Jor" for which no system identifier could be generated
    <a href="dreja.aspx?=hewal&jmara=50952&Jor=14" title="18/02/2013 ">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1877, Column 22: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start graphic--->
  • Info Line 1877, Column 1: comment declaration started here
    <!--- start graphic--->
  • Error Line 1891, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end graphic--->
  • Info Line 1891, Column 1: comment declaration started here
    <!--- end graphic--->
  • Error Line 1894, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end other --->
  • Info Line 1894, Column 1: comment declaration started here
    <!--- end other --->
  • Error Line 1912, Column 3: element "embed" undefined
      ></embed>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1919, Column 51: reference not terminated by REFC delimiter
    <a href="http://xendan.org/dreja.aspx?=hewal&jmara=42306&Jor=1">

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

  • Warning Line 1919, Column 51: reference to external entity in attribute value
    <a href="http://xendan.org/dreja.aspx?=hewal&jmara=42306&Jor=1">

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

  • Error Line 1919, Column 51: reference to entity "jmara" for which no system identifier could be generated
    <a href="http://xendan.org/dreja.aspx?=hewal&jmara=42306&Jor=1">

    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 787, Column 36: entity was defined here
        <li><a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)d…
  • Warning Line 1919, Column 61: reference not terminated by REFC delimiter
    <a href="http://xendan.org/dreja.aspx?=hewal&jmara=42306&Jor=1">

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

  • Warning Line 1919, Column 61: reference to external entity in attribute value
    <a href="http://xendan.org/dreja.aspx?=hewal&jmara=42306&Jor=1">

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

  • Error Line 1919, Column 61: reference to entity "Jor" for which no system identifier could be generated
    <a href="http://xendan.org/dreja.aspx?=hewal&jmara=42306&Jor=1">

    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 787, Column 48: entity was defined here
    …a  href="dreja.aspx?=hewal&jmara=51521&Jor=1"><img src="imgnews/1-(9)ddd282201…
  • Error Line 1932, Column 20: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start foot --->
  • Info Line 1932, Column 1: comment declaration started here
    <!--- start foot --->
  • Error Line 1938, Column 28: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start section hewal--->
  • Info Line 1938, Column 1: comment declaration started here
    <!--- start section hewal--->
  • Error Line 1954, Column 26: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end section hewal--->
  • Info Line 1954, Column 1: comment declaration started here
    <!--- end section hewal--->
  • Error Line 1956, Column 28: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start section sport--->
  • Info Line 1956, Column 1: comment declaration started here
    <!--- start section sport--->
  • Error Line 1961, Column 18: ID "mm" already defined
             <ul id="mm">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1943, Column 18: ID "mm" first defined here
             <ul id="mm">
  • Error Line 1968, Column 26: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end section sport--->
  • Info Line 1968, Column 1: comment declaration started here
    <!--- end section sport--->
  • Error Line 1972, Column 28: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start section radio--->
  • Info Line 1972, Column 1: comment declaration started here
    <!--- start section radio--->
  • Error Line 1977, Column 18: ID "mm" already defined
             <ul id="mm">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1943, Column 18: ID "mm" first defined here
             <ul id="mm">
  • Error Line 1986, Column 26: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end section radio--->
  • Info Line 1986, Column 1: comment declaration started here
    <!--- end section radio--->
  • Error Line 1989, Column 28: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start section xzmat--->
  • Info Line 1989, Column 1: comment declaration started here
    <!--- start section xzmat--->
  • Error Line 1994, Column 18: ID "mm" already defined
             <ul id="mm">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1943, Column 18: ID "mm" first defined here
             <ul id="mm">
  • Error Line 2004, Column 26: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end section xzmat--->
  • Info Line 2004, Column 1: comment declaration started here
    <!--- end section xzmat--->
  • Error Line 2007, Column 28: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start section about--->
  • Info Line 2007, Column 1: comment declaration started here
    <!--- start section about--->
  • Error Line 2012, Column 18: ID "mm" already defined
             <ul id="mm">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1943, Column 18: ID "mm" first defined here
             <ul id="mm">
  • Error Line 2019, Column 26: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end section about--->
  • Info Line 2019, Column 1: comment declaration started here
    <!--- end section about--->
  • Error Line 2021, Column 29: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start section reklam--->
  • Info Line 2021, Column 1: comment declaration started here
    <!--- start section reklam--->
  • Error Line 2026, Column 18: ID "mm" already defined
             <ul id="mm">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1943, Column 18: ID "mm" first defined here
             <ul id="mm">
  • Error Line 2032, Column 27: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end section reklam--->
  • Info Line 2032, Column 1: comment declaration started here
    <!--- end section reklam--->
  • Error Line 2034, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start search--->
  • Info Line 2034, Column 1: comment declaration started here
    <!--- start search--->
  • Error Line 2045, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end search--->
  • Info Line 2045, Column 1: comment declaration started here
    <!--- end search--->
  • Error Line 2048, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- start search--->
  • Info Line 2048, Column 1: comment declaration started here
    <!--- start search--->
  • Error Line 2057, Column 19: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end search--->
  • Info Line 2057, Column 1: comment declaration started here
    <!--- end search--->
  • Error Line 2061, Column 18: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--- end foot --->
  • Info Line 2061, Column 1: comment declaration started here
    <!--- end foot --->

Visitor Analysis

Daily Visitor
  • 14.117 visits