On 9/24/19 5:49 PM, Liam R E Quin wrote:
This isn’t true in general in XML, so beware.
That was why I was asking :-)
(And, it's why I really want LibXML2 to do as much of the thinking here
as possible!)
Thanks,
Webb
--
Webb Scales
Principal Software Architect
get something we
read until the ending tag and pause for processing. Eric
*From:*xml [mailto:xml-boun...@gnome.org] *On Behalf Of *Webb Scales
*Sent:* Monday, September 09, 2019 9:30 PM
*To:* Liam R E Quin ; xml@gnome.org
*Subject:* Re: [xml] Recovering from errors in an XML "stream&
, 2019 7:41 PM
To: Liam R. E. Quin ; xml@gnome.org
Subject: Re: [xml] Recovering from errors in an XML "stream"
On 9/7/19 12:37 AM, Liam R. E. Quin wrote:
On Fri, 2019-09-06 at 01:57 -0400, Webb Scales wrote:
The first issue is that the XML parser seems to balk entirely at
byte blocking and as
soon as we get something we read until the ending tag and pause for processing.
Eric
From: xml [mailto:xml-boun...@gnome.org] On Behalf Of Webb Scales
Sent: Monday, September 09, 2019 9:30 PM
To: Liam R E Quin ; xml@gnome.org
Subject: Re: [xml] Recovering from errors
On Tue, 2019-09-10 at 00:29 -0400, Webb Scales wrote:
>
> If the TextReader didn't insist upon reading beyond the root end-tag,
All XML parsers do that, as the spec requires them to check if anything
follows it and raise an error if so.
Liam
--
Liam Quin - web slave for
I'm OK with making small on-the-fly "edits" to the input (such as
removing the initial comment, or removing all comments), but trying to
make my code discern the overall structure (such as picking out the
boundaries between the documents) is starting to step over into actually
parsing it,
On Mon, 2019-09-09 at 22:41 -0400, Webb Scales wrote:
> the
> fact remains that I don't control the text that I'm trying to parse,
> and I still need to parse it, even though it's not "well-formed".
You may need to write some form of pre-processor that fixes the
problems. As you say, that may
On 9/7/19 12:37 AM, Liam R. E. Quin wrote:
On Fri, 2019-09-06 at 01:57 -0400, Webb Scales wrote:
The first issue is that the XML parser seems to balk entirely at the
fact that the document is preceded by a comment before the XML
declaration. (I'm less than shocked, but it is kind of
Greetings, all. My apologies if this has already been addressed...I had
no luck searching the archive.
My code is being presented with a stream of XML-like data which looks
similar to this:
\
\
\
\
I cannot read it all into memory, because it might be "big" or even
"infinite" in
