On Sat, Nov 24, 2007 at 11:55:03AM +0100, Stefan Behnel wrote:
>
> Stefan Behnel wrote:
> > I noticed a problem with the new way libxml2 2.6.29+ handles the HTML
> > "embed"
> > tag. It serialises it without the enclosing tag, which then lets following
> > attempts to parse the document fail, as
On Wed, Jul 02, 2008 at 03:08:59PM +0800, Ashwin wrote:
>
> > > ah, then it's a bug. i have tried to make sure the reader and the
> walker
> > > work the same, but i think I didn't tried that extensively for extra
> > > functionality like skipping part of the tree.
> > > Can you see why xmlTextR
On Fri, Jul 04, 2008 at 06:04:43PM +0800, Ashwin wrote:
>
> Hi Daniel,
>
>
> > An intermediate approach could have
> > been to start parsing directly from an immutable buffer based on the input
> > string and just switch to a small normal buffer when getting to the end of
> > the input. But in a
On Mon, Aug 25, 2008 at 08:12:49PM +0100, Martin (gzlist) wrote:
> On 25/08/2008, Boz <[EMAIL PROTECTED]> wrote:
> > 2008/8/25 Steven 黄 <[EMAIL PROTECTED]>:
> >
> > > I am a xml beginnner, and I am using libxml2 to edit some data for a
> > > system
> > > configuration file which doesn't contain (
Le 20 août 2008 à 23:34, Andi Sidwell a écrit :
FWIW, I've spent the summer working on a C HTML5 parser which is
approaching stability, called Hubbub[1]. It's about as half as fast
as
libxml2 at parsing the HTML 5 spec with an O(1) treebuilder, and it's
fairly easy to bind to the libxml2 int
On Mon, Aug 25, 2008 at 09:47:32PM +0200, Mike Hommey wrote:
> On Sun, Aug 24, 2008 at 10:51:59AM +0200, Daniel Veillard wrote:
> > On Sun, Aug 24, 2008 at 10:15:41AM +0200, Mike Hommey wrote:
> > > On Wed, Aug 20, 2008 at 07:00:51PM +0200, Daniel Veillard wrote:
> > > > Bad news, when checking a
On Sun, Aug 24, 2008 at 10:51:59AM +0200, Daniel Veillard wrote:
> On Sun, Aug 24, 2008 at 10:15:41AM +0200, Mike Hommey wrote:
> > On Wed, Aug 20, 2008 at 07:00:51PM +0200, Daniel Veillard wrote:
> > > Bad news, when checking against recursive entities expansion problem
> > > back when it was ma
On 25/08/2008, Boz <[EMAIL PROTECTED]> wrote:
> 2008/8/25 Steven 黄 <[EMAIL PROTECTED]>:
>
> > I am a xml beginnner, and I am using libxml2 to edit some data for a system
> > configuration file which doesn't contain (all elements
> > in this xml are quite standard). Even Though adding this tag to
On 25/08/2008, Niels Van Hoef <[EMAIL PROTECTED]> wrote:
>
> I tried you suggestion even before posting this question but a small
> test program yields the following results:
>
>
>
> element
>
This looks like you've passed a pointer to an empty string, rather
than a null pointer.
> Whe
2008/8/25 Steven 黄 <[EMAIL PROTECTED]>:
> I am a xml beginnner, and I am using libxml2 to edit some data for a system
> configuration file which doesn't contain (all elements
> in this xml are quite standard). Even Though adding this tag to the file has
> no effect on anything, I still don't like t
I am a xml beginnner, and I am using libxml2 to edit some data for a system
configuration file which doesn't contain (all elements in
this xml are quite standard). Even Though adding this tag to the file has no
effect on anything, I still don't like to add it.
Currently I do this:
xmlparsef
Under certain circumstances a CharRef is resolved twice which leads
to a wrong interpretation of some regular expressions in XML Schemas.
The attached patch fixes this bug by removing some superfluous code
and adding appropriate unit tests. In addition to this patch, you
need to create two empty f
I found a small typo in an libxml2 error message. It is fixed
by the attached patch.
More details: http://bugzilla.gnome.org/show_bug.cgi?id=542634
Greets,
Volker
--
Volker Grabsch
---<<(())>>---
Administrator
NotJustHosting GbR
http://bugzilla.gnome.org/show_bug.cgi?id=542634
Index: li
Hi Martin,
Thanks for the replay and the note about setting the namespace for the
root node. This was another porblem I was having.
I tried you suggestion even before posting this question but a small
test program yields the following results:
element
Where as I would suspect:
element
14 matches
Mail list logo