These 2 files have an element PruningSection which contain en element
Channels that contains some text. These 2 files are extremely similar
and I dont think they should be creating a node Tree any different than
each other.
1) Why are these coming out different?
2) Is there a method (or
using libxml2 2.6.26
David Grohmann wrote:
These 2 files have an element PruningSection which contain en
element Channels that contains some text. These 2 files are
extremely similar and I dont think they should be creating a node Tree
any different than each other.
1) Why are these coming
David Grohmann wrote:
These 2 files have an element PruningSection which contain en
element Channels that contains some text. These 2 files are
extremely similar and I dont think they should be creating a node Tree
any different than each other.
Yes, they should. Whitespace between XML
Jason Viers wrote:
David Grohmann wrote:
These 2 files have an element PruningSection which contain en
element Channels that contains some text. These 2 files are
extremely similar and I dont think they should be creating a node
Tree any different than each other.
Yes, they
Jason Viers wrote:
Jason Viers wrote:
David Grohmann wrote:
These 2 files have an element PruningSection which contain en
element Channels that contains some text. These 2 files are
extremely similar and I dont think they should be creating a node
Tree any different than each
Jason Viers wrote:
Jason Viers wrote:
David Grohmann wrote:
These 2 files have an element PruningSection which contain en
element Channels that contains some text. These 2 files are
extremely similar and I dont think they should be creating a node
Tree any different than each
David Grohmann wrote:
the call I'm using is this
xmlReadFile( document_filename, NULL, XML_PARSE_PEDANTIC )
are you saying that if i change XML_PARSE_PEDANTIC to
XML_PARSE_NOBLANKS it will parse them exactly the same?
They SHOULD be parsing the same anyway, don't know why they're not.
David Grohmann wrote:
But is there a better way to get at that data than manually following
pointers like I was showing in the GDB prompts?
Nope, following children and next pointers is the way you get around
the trees.
Jason
___
xml mailing list,
On Wed, 2007-21-02 at 15:59 -0600, David Grohmann wrote:
[...] .But is there a better way to get at that data than manually
following pointers like I was showing in the GDB prompts?
The XPath interface is higher level, if that helps.
Liam
--
Liam Quin - XML Activity Lead, W3C,
Jason Viers wrote:
David Grohmann wrote:
But is there a better way to get at that data than manually following
pointers like I was showing in the GDB prompts?
Nope, following children and next pointers is the way you get around
the trees.
Jason
10 matches
Mail list logo