prairieprog wrote:I am e-mailing the files.
Thanks for those.
This is a cute problem
If you're not technical, you can just scroll down to the end of this post where I say I'm not sure what to do
A lot of the feeds you posted are coming from WordPress blogs which appears to have a bug in that it is using <tt>&#8217;</tt> to represent a quote, even though it is wrapping the item descriptions in CDATA markers. The other non-WordPress feeds are making the same (or a similar) misteak.
I won't go into the gory details but Awasu is smart enough to know whether an item description is plain text or a piece of HTML and encodes it accordingly when generating the channel's HTML page.
You're seeing this problem because you've got those channels to show excerpts. If they were showing full content, Awasu just dumps the items into the HTML page and when the browser sees the <tt>&#8217;</tt>, it converts it to a quote. But when excerpting, Awasu <u>converts the item description to plain-text</u> before truncating it. Then, when it comes to inserting it into the channel's HTML page, Awasu sees there's an ampersand in there, knows that the browser is going to try to interpret it as an SGML entity, and so encodes it so that it won't.
This has only started happening recently because all this sophisticated plain text vs. HTML handling of content was introduced in 2.2.1
So, ultimately the problem is being caused by invalid feeds and you're seeing it because you've got the feeds configured to show excerpts. This is something I'd like to get Awasu to automatically detect and rectify but it's a little tricky. I'll have a ponder over it.
In the short-term, you can either show full content or there is a debug switch you can turn on that hacks the feed parsing process but it might cause problems in the future so I'll see if I can't work around the problem first.