After looking into this more myself, I'm thinking that it could be a problem with a bogus time format on the Buffalo News Atom feed. Here's what the feed looks like:
Code:
<item>
<title>Mold risk could stall courthouse opening</title>
<link>http://www.buffalonews.com/city/communities/downtown/article361082.ece</link>
<description>Mysterious moisture problem in building's walls poses health hazard, concerns federal officials</description>
<pubDate>Tue, 08 Mar 2011 10:08:23 -0500</pubDate>
<guid>http://www.buffalonews.com/city/communities/downtown/article361082.ece</guid>
</item>
I noticed on the feedparser site that the date listed in the pubDate tag is not a standard date. Therefore I believe this issue may have something to do with the UTC conversion of the date? The
feedparser site does not show this format as being a recognized format and it's probably spitting out something that is off 14 hours as a result. Thoughts and guidance? It seems like a custom date handler would have to be written.
I'm hoping someone can chime in on if they think I'm on the right or wrong path. I know there has been some discussion about dates and conversion (Kindle formats, etc.), but this clearly has to do with a recipe process. Has anyone implemented a custom date handler in another recipe I can look at?
Thanks,
Chappy