Emit some sort of error. Make it something that's not a show-stopper but don't
just silently cobble up a work around. Stick a big-Red-X on the treeview. But
do /something/ to let them know that something's amiss.
That and consider doing some sort of lookups for them. We run a web service
that you can use to check a feed's known condition. But basically, don't just
do nothing and silently cobble up a work-around.
----- Original Message -----
From: "Dare Obasanjo" <>
The issue isn't whether they are bugs in the generator. The question is
whether an aggregator should [for example] try each of the heuristics
below to try to parse an XML document instead of giving Joe User an ugly
error message because the Ziff Davis Microsoft-Watch or National
Geographic RSS feed doesn't specify the correct encoding in the XML
declaration.
