[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 139302] incorrect parsing of some RSS feeds
From:       Mathieu Bonnet <mathieu.bonnet () riverside-idealism ! org>
Date:       2006-12-29 11:38:28
Message-ID: 20061229113828.29539.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=139302         




------- Additional Comments From mathieu.bonnet riverside-idealism org  2006-12-29 \
12:38 ------- It might be something similar to bug #139043, though I cannot find date \
problems with http://feeds.feedburner.com/Hullabaloo (nor with \
http://blog.beryl-project.org/?feed=rss2 from the other bug report).

Chet, do you have the same problem with \
"http://www.tatanka.com.br/ies4linux/news/feed/"? (check comment 1, from the other \
bug report, for what problems I encounter).

I tried to find the problem myself, but I had some difficulty building a working \
development environment (well, not that I really searched for documentation), so I \
gave up.

In "kdepim-3.5.5/akregator/src/librss/", file "article.cpp", lines from 114 to 140, \
is the place where dates are extracted and converted.

In the same directory, file "tools_p.cpp", lines 20 to 31, is defined the \
"parseISO8601Date()" function (from Atom, so it shouldn't be used for RSS 2.0 feeds).

In "kdelibs-3.5.5/kdecode/", file "krfcdate.cpp", is defined the function \
"KRFCDate::parseDate()", which is probably where there might be some problem, if it \
is not a global parsing problem.

A basic workaround -well, the problem should probably be easy to find, with a working \
development environment- (could it be implemented for kde-3.5.6? bugs can still be \
corrected, right?), would be to detect some parsing problems, like a date too far in \
the past or in the future, and simply do not set this date, and keep the default \
fetch date... (and do the same, when only the time is detected -badly-, like " \
00:00").


[prev in list] [next in list] [prev in thread] [next in thread]