w3 Validate

Merhaba arkadaşlar ben,
şeklinde link vermiştim. Ancak w3 bunu hata olarak görüyor
Hemde 37-38 kere

Hata:
# Warning Line 30, Column 66: cannot generate system identifier for general entity "hl"

…ranslate.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr…

?

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 "&" (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 æ 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 30, Column 66: general entity "hl" not defined and no default entity

…ranslate.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr…

?

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 30, Column 68: reference not terminated by REFC delimiter

…nslate.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&t…

?

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Error Line 30, Column 68: reference to entity "hl" for which no system identifier could be generated

…nslate.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&t…

?

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 30, Column 65: entity was defined here

…translate.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=t…

# Warning Line 30, Column 72: cannot generate system identifier for general entity "u"

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en…

?

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 "&" (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 æ 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 30, Column 72: general entity "u" not defined and no default entity

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en…

?

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 30, Column 73: reference not terminated by REFC delimiter

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

?

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Error Line 30, Column 73: reference to entity "u" for which no system identifier could be generated

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

?

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 30, Column 71: entity was defined here

…ate.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=e…

# Warning Line 30, Column 101: cannot generate system identifier for general entity "sl"

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

?

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 "&" (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 æ 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 30, Column 101: general entity "sl" not defined and no default entity

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

?

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 30, Column 103: reference not terminated by REFC delimiter

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

?

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Error Line 30, Column 103: reference to entity "sl" for which no system identifier could be generated

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

?

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 30, Column 100: entity was defined here

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

# Warning Line 30, Column 107: cannot generate system identifier for general entity "tl"

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

?

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 "&" (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 æ 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 30, Column 107: general entity "tl" not defined and no default entity

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

?

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 30, Column 109: reference not terminated by REFC delimiter

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

?

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Error Line 30, Column 109: reference to entity "tl" for which no system identifier could be generated

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

?

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 30, Column 106: entity was defined here

…te.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=en"

# Warning Line 34, Column 68: reference not terminated by REFC delimiter

…nslate.google.com/translate?prev=hp&hl=ru&u=www.siteadi.com/index.php&sl=tr&t…

?

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Error Line 34, Column 68: reference to entity "hl" for which no system identifier could be generated

…nslate.google.com/translate?prev=hp&hl=ru&u=www.siteadi.com/index.php&sl=tr&t…

?

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 30, Column 65: entity was defined here

…translate.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=t…

# Warning Line 34, Column 73: reference not terminated by REFC delimiter

…te.google.com/translate?prev=hp&hl=ru&u=www.siteadi.com/index.php&sl=tr&tl=ru"

?

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Error Line 34, Column 73: reference to entity "u" for which no system identifier could be generated

…te.google.com/translate?prev=hp&hl=ru&u=www.siteadi.com/index.php&sl=tr&tl=ru"

?

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 30, Column 71: entity was defined here

…ate.google.com/translate?prev=hp&hl=en&u=www.siteadi.com/index.php&sl=tr&tl=e…

# Warning Line 34, Column 103: reference not terminated by REFC delimiter

…te.google.com/translate?prev=hp&hl=ru&u=www.siteadi.com/index.php&sl=tr&tl=ru"

?

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Error Line 34, Column 103: reference to entity "sl" for which no system identifier could be generated

…te.google.com/translate?prev=hp&hl=ru&u=www.siteadi.com/index.php&sl=tr&tl=ru"

?

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.

Bu sadece bir kısmı

Böyle denermisiniz.

__________________
Banner Tasarımlarınız Yapılır! İletişim: Özel Mesaj | Referans

# Warning Line 1, Column 56: cannot generate system identifier for general entity "amp"

…ranslate.google.com/translate?prev=hp&hl=en&u=http://www.siteadi.com&a…

✉

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 "&" (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 æ 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 1, Column 56: general entity "amp" not defined and no default entity

…ranslate.google.com/translate?prev=hp&hl=en&u=http://www.siteadi.com&a…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Error Line 1, Column 59: reference to entity "amp" for which no system identifier could be generated

…slate.google.com/translate?prev=hp&hl=en&u=http://www.siteadi.com&…

✉

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 1, Column 55: entity was defined here

…translate.google.com/translate?prev=hp&hl=en&u=http://www.siteadi.com&…

# Error Line 1, Column 69: reference to entity "amp" for which no system identifier could be generated

…le.com/translate?prev=hp&hl=en&u=http://www.siteadi.com&sl=tr&…

✉

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 1, Column 55: entity was defined here

…translate.google.com/translate?prev=hp&hl=en&u=http://www.siteadi.com&…

# Error Line 1, Column 98: reference to entity "amp" for which no system identifier could be generated

…ev=hp&amp;hl=en&amp;u=http://www.siteadi.com&amp;sl=tr&amp;tl=en">translate</a>

✉

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 1, Column 55: entity was defined here

…translate.google.com/translate?prev=hp&amp;hl=en&amp;u=http://www.siteadi.com&…

# Error Line 1, Column 108: reference to entity "amp" for which no system identifier could be generated

…ev=hp&amp;hl=en&amp;u=http://www.siteadi.com&amp;sl=tr&amp;tl=en">translate</a>

✉

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 1, Column 55: entity was defined here

…translate.google.com/translate?prev=hp&amp;hl=en&amp;u=http://www.siteadi.com&…




Malesef olmadı