No entiendo éstos errores Los errores son los siguientes:
Cita:
Si alguien me puede ayudar le agradecería muchísimo ;)Validation Output: 10 Errors
1. Warning Line 84, Column 125: cannot generate system identifier for general entity "los_i".
…'); return false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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.
2. Error Line 84, Column 125: general entity "los_i" not defined and no default entity.
…'); return false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
3. Warning Line 84, Column 130: reference not terminated by REFC delimiter.
…eturn false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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.
4. Warning Line 84, Column 130: reference to external entity in attribute value.
…eturn false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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 '&'.
5. Error Line 84, Column 130: reference to entity "los_i" for which no system identifier could be generated.
…eturn false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
6. Info Line 84, Column 124: entity was defined here.
…1'); return false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
7. Warning Line 84, Column 135: cannot generate system identifier for general entity "win_f".
… false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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.
8. Error Line 84, Column 135: general entity "win_f" not defined and no default entity.
… false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
9. Warning Line 84, Column 140: reference not terminated by REFC delimiter.
…e;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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.
10. Warning Line 84, Column 140: reference to external entity in attribute value.
…e;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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 '&'.
11. Error Line 84, Column 140: reference to entity "win_f" for which no system identifier could be generated.
…e;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
12. Info Line 84, Column 134: entity was defined here.
…n false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
13. Warning Line 93, Column 108: reference not terminated by REFC delimiter.
…return false;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
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.
14. Warning Line 93, Column 108: reference to external entity in attribute value.
…return false;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
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 '&'.
15. Error Line 93, Column 108: reference to entity "los_i" for which no system identifier could be generated.
…return false;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
16. Info Line 84, Column 124: entity was defined here.
…1'); return false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
17. Warning Line 93, Column 119: reference not terminated by REFC delimiter.
…e;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
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.
18. Warning Line 93, Column 119: reference to external entity in attribute value.
…e;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
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 '&'.
19. Error Line 93, Column 119: reference to entity "win_f" for which no system identifier could be generated.
…e;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
20. Info Line 84, Column 134: entity was defined here.
…n false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
21. Error Line 84, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…cript:cargar('1334','137','686512099475353101'); return false;" href="?win_i=…
✉
22. Error Line 84, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…cript:cargar('1334','137','686512099475353101'); return false;" href="?win_i=…
✉
23. Error Line 93, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…1334','58271208384842659'); return false;" href="?win_i=137&los_i=1334&win_f=…
✉
24. Error Line 93, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…1334','58271208384842659'); return false;" href="?win_i=137&los_i=1334&win_f=…
1. Warning Line 84, Column 125: cannot generate system identifier for general entity "los_i".
…'); return false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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.
2. Error Line 84, Column 125: general entity "los_i" not defined and no default entity.
…'); return false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
3. Warning Line 84, Column 130: reference not terminated by REFC delimiter.
…eturn false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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.
4. Warning Line 84, Column 130: reference to external entity in attribute value.
…eturn false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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 '&'.
5. Error Line 84, Column 130: reference to entity "los_i" for which no system identifier could be generated.
…eturn false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
6. Info Line 84, Column 124: entity was defined here.
…1'); return false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
7. Warning Line 84, Column 135: cannot generate system identifier for general entity "win_f".
… false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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.
8. Error Line 84, Column 135: general entity "win_f" not defined and no default entity.
… false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
9. Warning Line 84, Column 140: reference not terminated by REFC delimiter.
…e;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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.
10. Warning Line 84, Column 140: reference to external entity in attribute value.
…e;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
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 '&'.
11. Error Line 84, Column 140: reference to entity "win_f" for which no system identifier could be generated.
…e;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
12. Info Line 84, Column 134: entity was defined here.
…n false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
13. Warning Line 93, Column 108: reference not terminated by REFC delimiter.
…return false;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
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.
14. Warning Line 93, Column 108: reference to external entity in attribute value.
…return false;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
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 '&'.
15. Error Line 93, Column 108: reference to entity "los_i" for which no system identifier could be generated.
…return false;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
16. Info Line 84, Column 124: entity was defined here.
…1'); return false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
17. Warning Line 93, Column 119: reference not terminated by REFC delimiter.
…e;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
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.
18. Warning Line 93, Column 119: reference to external entity in attribute value.
…e;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
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 '&'.
19. Error Line 93, Column 119: reference to entity "win_f" for which no system identifier could be generated.
…e;" href="?win_i=137&los_i=1334&win_f=5827120838484265 9">
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
20. Info Line 84, Column 134: entity was defined here.
…n false;" href="?win_i=1334&los_i=137&win_f=6865120994753531 01">
21. Error Line 84, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…cript:cargar('1334','137','686512099475353101'); return false;" href="?win_i=…
✉
22. Error Line 84, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…cript:cargar('1334','137','686512099475353101'); return false;" href="?win_i=…
✉
23. Error Line 93, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…1334','58271208384842659'); return false;" href="?win_i=137&los_i=1334&win_f=…
✉
24. Error Line 93, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…1334','58271208384842659'); return false;" href="?win_i=137&los_i=1334&win_f=…
Saludos!
