On Fri, Jun 29, 2007 at 09:32:10PM +0200, Lars Lindner wrote: > > > With XML the rule is applications should *ALWAYS* refuse non-wellformed > > > content. Also when using a library for parsing the application has no > > > way to force tolerant parsing. As for libxml2 I know for sure that the > > > author clearly disagrees with applications wanting to do tolerant parsing. > > > > In any case, previous versions of liferea were able to display these > > common entries without trouble. I don't know if that means it did not > > push article bodies through libxml2; I think it somewhat likely, since > > this is the escaped contents of the <description>, not part of the RSS > > feed proper. Normally that's HTML, with all the attendant sloppiness, > > rather than well-formed XML. > > The reason is that the 1.0.x series did generate HTML for rendering. > 1.2.x uses XHTML which automatically includes namespace checks. And to > be honest I see no easy solution for embedded namespaces. Is the feed > reader to be expected to extract and merge namespaces defined by the > feed (and different ones over time!) into the XHTML generated to > render items? I think it is technically possible, but also really > troublesome.
I see. We don't have any marker indicating what sort of data the <description> is, unfortunately. I think expecting it to be well-formed XHTML may be... a little overly optimistic, given the sorts of things that generate RSS feeds. Maybe there's some manual way to avoid this problem - allowing the user to manually bind a specific prefix? If there isn't, I can hack up a filter for my local LJ feeds. But it would be nice if it worked out of the box. -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
