On 26 Aug, 23:22, "bruce" <[EMAIL PROTECTED]> wrote:
>
> ok, i can somehow live with this, i can accommodate it. but tell me, when
> the parse module/class for libxml2dom does its thing, why does it not go
> forward on the tree when it comes to a , if there's more text in the
> string to process???
ython-list@python.org
Subject: Re: libxml2dom - parsing maligned html
On 26 Aug, 17:28, "bruce" <[EMAIL PROTECTED]> wrote:
> so it's as if the parseString only reads the initial "html" tree. i've
> reviewed as much as i can find regarding libxml2dom to
bruce wrote:
> I'm using quick test with libxml2dom
>
> ===
> import libxml2dom
>
> aa=libxml2dom.parseString(foo)
> ff=libxml2dom.toString(aa)
>
> print ff
> ===
>
> --
> when i start, foo is:
>
>
>
>
>
>
>
> .
> .
> .
>
>
>
On 26 Aug, 17:28, "bruce" <[EMAIL PROTECTED]> wrote:
> so it's as if the parseString only reads the initial "html" tree. i've
> reviewed as much as i can find regarding libxml2dom to try to figure out how
> i can get it to read/parse/handle both html trees/nodes.
Maybe there's some possibility to
Hi...
I'm using quick test with libxml2dom
===
import libxml2dom
aa=libxml2dom.parseString(foo)
ff=libxml2dom.toString(aa)
print ff
===
--
when i start, foo is:
.
.
.
---
when i print ff it's:
