Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[masamasa]

I've been experiencing a podcast format error with some feeds, like:

http://rss.cnn.com/services/podcasting/newscast/rss.xml

The error message is "This podcast feed is not currently available, or contains a data format error." So I turned on logging and I got:

4250031: 3940: Podcast: CPodcastFeed::DownloadComplete: Start
4250047: 3940: Podcast: CPodcastFeed::DownloadComplete: URL: http://rss.cnn.com/services/podcasting/newscast/rss.xml
4250047: 3940: Podcast: CPodcastFeed::DownloadComplete: Finish (16 ms)
4250047: 2968: General: CMJFileListCtrl::StartFileInsertion: Start
4250047: 3940: Podcast: CPodcastWorker::HandleWorkComplete: XML Field Error: item 1 episode: 1 tag=pubDate value=Mon, 11 Feb 2008 03:16:13 EST

But the date format looks good to me.

Some other feeds, like http://downloads.bbc.co.uk/podcasts/radio/newspod/rss.xml work OK.

I've been seeing this symptom since around 12.0.404. Any clue?

[JimH]

Did you try updating MC?

Can you let CNN know there may be a problem?

[masamasa]

Yes, I tried the latest one. No change.

I checked their XML, but I didn't see anything wrong with their <pubDate> items which do follow the RFC 822 date-time format. And the feed works with both IE7 and Firefox.

Does the feed work with your MC12 installation?

[John Gateley]

I just loaded the feed, no problems. Please post your system info.

j

[masamasa]

I realized that it works if I change the locale (language and country) setting on my Windows Vista. It works OK in en_US (English/U.S.) locale. But it doesn't in ja_JP (Japanese/Japan) locale.

I suspect that the date-time parsing in MC12 is somehow locale-dependent.

[JimH]

Good find.  Thanks.  Look for a fix in one of the next public builds here.

[John Gateley]

I suspect that the date-time parsing in MC12 is somehow locale-dependent.

Yes. In Japanese, the abbreviation for January is not a shortened word (in English it would be "Jan"), it is the number "1".
This led to confusion in the date parsing. Fixed soon.

Thanks for finding this...

j