Käytän sivullani mureakuhasta lainattua RSS-feedin parseria :http://mureakuha.com/koodikirjasto/765.
Ongelmana on että sivuni menevät muuten läpi xhmtl 1.0 transitional validoinnista mutta tuo parserin tuottama koodi aiheuttaa useita virheitä. Onko tämä asiaan kuuluvaa ko. parserin kanssa vai olenko ns. kädettänyt jotain ?
No mitä virheitä validaattori antaa? Tarkistat vain mitä parseri tulostaa ja muokkaat sitä niin, että se on validia..
Below are the results of checking this document for XML well-formedness and validity.
1. Warning Line 65 column 590: cannot generate system identifier for general entity "code_art".
...www.lemessager.net/details_articles.php?code=110&code_art=12758">Le Syndicat
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 65 column 590: general entity "code_art" not defined and no default entity.
...www.lemessager.net/details_articles.php?code=110&code_art=12758">Le Syndicat
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 65 column 598: reference not terminated by REFC delimiter.
...ssager.net/details_articles.php?code=110
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 65 column 598: reference to external entity in attribute value.
...ssager.net/details_articles.php?code=110
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 65 column 598: reference to entity "code_art" for which no system identifier could be generated.
...ssager.net/details_articles.php?code=110
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 65 column 589: entity was defined here.
.../www.lemessager.net/details_articles.php?code=110&code_art=12758">Le Syndicat
7. Warning Line 65 column 1358: cannot generate system identifier for general entity "oid".
....kauppalehti.fi/4/i/uutiset/stt/juttu.jsp?
✉
8. Error Line 65 column 1358: general entity "oid" not defined and no default entity.
....kauppalehti.fi/4/i/uutiset/stt/juttu.jsp?
✉
9. Warning Line 65 column 1361: reference not terminated by REFC delimiter.
...uppalehti.fi/4/i/uutiset/stt/juttu.jsp?
✉
10. Warning Line 65 column 1361: reference to external entity in attribute value.
...uppalehti.fi/4/i/uutiset/stt/juttu.jsp?
✉
11. Error Line 65 column 1361: reference to entity "oid" for which no system identifier could be generated.
...uppalehti.fi/4/i/uutiset/stt/juttu.jsp?
✉
12. Info Line 65 column 1357: entity was defined here.
...w.kauppalehti.fi/4/i/uutiset/stt/juttu.jsp?
Valid XHTML 1.0! The W3C Validator Team
Aihe on jo aika vanha, joten et voi enää vastata siihen.