页面引用了script的统计，w3.org验证时出错！

ＱＱ糖

页面引用了script的统计，w3.org验证时出错！
页面底部加了两个统计，
<script language="JavaScript" src="http://s33.cnzz.com/stat.php?id=108437Web_id=108437&Show=pic" charset="gb2312" type="text/javascript"></script>
    <script language="JavaScript" src="http://www1.itsun.com/count.php?Uuid=1617957Style=icon" charset="gb2312" type="text/javascript"></script>


在
http://validator.w3.org
验证时就包错！！


Warning Line 210 column 78: cannot generate system identifier for general entity "Web_id".
...tp://s33.cnzz.com/stat.php?id=108437Web_id=108437&Show=pic" charset="gb2312"
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 210 column 78: general entity "Web_id" not defined and no default entity.
...tp://s33.cnzz.com/stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312"
This is usually a cascading error caused by 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 210 column 84: reference not terminated by REFC delimiter.
...33.cnzz.com/stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312" type=
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 210 column 84: reference to external entity in attribute value.
...33.cnzz.com/stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312" type=
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 210 column 84: reference to entity "Web_id" for which no system identifier could be generated.
...33.cnzz.com/stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312" type=
This is usually a cascading error caused by 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 210 column 77: entity was defined here.
...ttp://s33.cnzz.com/stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312
Warning Line 210 column 92: cannot generate system identifier for general entity "Show".
...com/stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312" type="text/ja
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 210 column 92: general entity "Show" not defined and no default entity.
...com/stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312" type="text/ja
This is usually a cascading error caused by 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 210 column 96: reference not terminated by REFC delimiter.
...stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312" type="text/javasc
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 210 column 96: reference to external entity in attribute value.
...stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312" type="text/javasc
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 210 column 96: reference to entity "Show" for which no system identifier could be generated.
...stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312" type="text/javasc
This is usually a cascading error caused by 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 210 column 91: entity was defined here.
....com/stat.php?id=108437&Web_id=108437&Show=pic" charset="gb2312" type="text/j
Warning Line 211 column 84: cannot generate system identifier for general entity "Style".
...ww1.itsun.com/count.php?Uuid=1617957&Style=icon" charset="gb2312" type="text/
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 211 column 84: general entity "Style" not defined and no default entity.
...ww1.itsun.com/count.php?Uuid=1617957&Style=icon" charset="gb2312" type="text/
This is usually a cascading error caused by 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 211 column 89: reference not terminated by REFC delimiter.
...tsun.com/count.php?Uuid=1617957&Style=icon" charset="gb2312" type="text/javas
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 211 column 89: reference to external entity in attribute value.

...tsun.com/count.php?Uuid=1617957&Style=icon" charset="gb2312" type="text/javas
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 211 column 89: reference to entity "Style" for which no system identifier could be generated.
...tsun.com/count.php?Uuid=1617957&Style=icon" charset="gb2312" type="text/javas
This is usually a cascading error caused by 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 211 column 83: entity was defined here.
...www1.itsun.com/count.php?Uuid=1617957&Style=icon" charset="gb2312" type="text

timmy

呵呵，如果我也能像话裳这样利害就好了，最佩服她了。