In response to the mail by Pierre Habouzit dated 25 January 2005 at 14:10:
| Le Mardi 25 Janvier 2005 13:20, Dirk Eddelbuettel a écrit :
| > Package: akregator
| > Version: 1.0-beta8-2
| > Severity: important
| >
| > Salut Pierre,
| >
| > Thanks for looking akregator -- a great rss reader.  Once in a while,
| > and in particular on Debian Planet, someone puts a '&' into a story
| > heading. Currently this can be seen on planet.debian.org in the story
| > from Marga.
| >
| > Akregator then stops updating the feed. This is rather annoying.  I
| > discussed this with the authors of the planet code, and their take is
| > that their Python toolset, in particular the rss part, is robust --
| > it is the readers that are at fault.
| 
|   they are wrong.
| 
|   I don't say that akregator should'nt be more robust to bad encoded 
| entities, but the spec for RSS is xml, and in xml you have to put 
| things like that :
| 
|  <tag>put an ampersand : &amp;</tag>
| 
| OR
| 
|  <tag><![CDATA[put an ampersand : &]]></tag>
| 
| any other solution is NOT correct, so you can bug debianplanet too. or 
| the python module they use.

Can't resist CCing Scott here as I pestered him (unsuccessfully) about this 
before.
 
|   the bug is well known ([1] : funny, it is a debian planet problem 
| too), and is Qt's fault, since akregator uses the Qt xml API that has a 
| very strict (but also correct) parser.

Well, is someone going to fix it?
  
| anyway, the bug is certainly not important, at most normal, since it 
| only stop the fetch of the faulty feed, and not of the others.

Don't disagree completely but reading Planet Debian is important to me, and I
can't read it right now. As our lusers break the content, how about if both
ends of the software strive to get better here?

Dirk
 
| 
| 
|  [1] http://bugs.kde.org/show_bug.cgi?id=86535
| -- 
| ·O·  Pierre Habouzit
| ··O
| OOO                                                http://www.madism.org

-- 
Better to have an approximate answer to the right question than a precise 
answer to the wrong question.  --  John Tukey as quoted by John Chambers

Reply via email to