On Fri, Sep 21, 2007 at 12:50:19AM +0200, Lars Lindner wrote:
Thanks for the link. It helped me to create a solution. Now Liferea
copies all global namespace definitions to the generated XHTML root
node. This solves the problem for me.
Fix available in SVN to be released with 1.4.3
Thanks
On 6/29/07, Daniel Jacobowitz [EMAIL PROTECTED] wrote:
On Fri, Jun 29, 2007 at 10:37:38PM +0200, Lars Lindner wrote:
For correctness LJ should provide Atom feeds which wrap everything in a
div lj:ns=http://livejournal.com/something;
Of course prefix lj and URL are fictional and should
On Thu, Sep 20, 2007 at 11:57:50PM +0200, Lars Lindner wrote:
Yes, it is. I've thought a while over it and I think it is a good idea
to treat global namespaces and add them to the extracted feed items
content.
Great! Thanks for getting back to me.
What I'm missing at the moment is a
On Fri, Sep 21, 2007 at 12:50:19AM +0200, Lars Lindner wrote:
Thanks for the link. It helped me to create a solution. Now Liferea
copies all global namespace definitions to the generated XHTML root
node. This solves the problem for me.
Fix available in SVN to be released with 1.4.3
Thanks!
On 9/21/07, Daniel Jacobowitz [EMAIL PROTECTED] wrote:
On Thu, Sep 20, 2007 at 11:57:50PM +0200, Lars Lindner wrote:
Yes, it is. I've thought a while over it and I think it is a good idea
to treat global namespaces and add them to the extracted feed items
content.
Great! Thanks for
On 6/29/07, Daniel Jacobowitz [EMAIL PROTECTED] wrote:
Package: liferea
Version: 1.2.16b-1
Followup-For: Bug #430782
The error message is accurate:
XML Parsing Error: prefix not bound to a namespace
Location: file:///
Line Number 450, Column 119:
The XML isn't valid,
On Fri, Jun 29, 2007 at 08:59:37PM +0200, Lars Lindner wrote:
You are correct this is an error message given by libxml2.
But you are totally wrong about handling invalid XML. The core
idea of XML is to guarantee applications a correct content encoding
by ensuring well-formedness and validity
On 6/29/07, Daniel Jacobowitz [EMAIL PROTECTED] wrote:
On Fri, Jun 29, 2007 at 08:59:37PM +0200, Lars Lindner wrote:
You are correct this is an error message given by libxml2.
But you are totally wrong about handling invalid XML. The core
idea of XML is to guarantee applications a correct
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
On 6/29/07, Daniel Jacobowitz [EMAIL PROTECTED] wrote:
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
On Fri, Jun 29, 2007 at 10:37:38PM +0200, Lars Lindner wrote:
For correctness LJ should provide Atom feeds which wrap everything in a
div lj:ns=http://livejournal.com/something;
Of course prefix lj and URL are fictional and should be replaced
with the real values I do not know.
I've run in to the same problem and I can add some observations. It's
not just LiveJournal feeds that generate this error message from
libxml2. I'm dealing with a malformed feed hosted by Typepad that's
causing the same problem.
Also, if I try to read such a feed in Combined View it will
Package: liferea
Version: 1.2.16b-1
Followup-For: Bug #430782
The error message is accurate:
XML Parsing Error: prefix not bound to a namespace
Location: file:///
Line Number 450, Column 119:
The XML isn't valid, but many feeds seem to have this level of
inaccuracy and
13 matches
Mail list logo
