Lists Home |
Date Index |
- From: Chris Lovett <email@example.com>
- To: 'Jarle Stabell' <firstname.lastname@example.org>, email@example.com
- Date: Fri, 7 Nov 1997 09:46:48 -0800
The Object Model in MSXML handles this by providing a convenience getText()
function on all Element nodes that returns the concatenated text. If
someone really wants to see the entity ref nodes, they can enumerate the
child nodes and find them. This way the client decides what they want.
> -----Original Message-----
> From: Jarle Stabell [SMTP:firstname.lastname@example.org]
> Sent: Friday, November 07, 1997 9:44 AM
> To: email@example.com
> Subject: Re: XML processing experiments
> David McKelvie wrote:
> >>> "<!ENTITY name 'richard'> ... <p>my name is &name;</p>"
> >It's worth pointing out that Richard wants ALL of the PCDATA of the
> ><p> element to be returned as one string of characters "my name is
> >Richard", rather than as two strings "my name is " and "Richard".
> Yes. But this requires one to copy (at least the first string) and a
> Some applications may be more interested in the speedup which may result
> from not doing this copying/concatenation, and happily accept the small
> increase in complexity handling it.
> I'm playing with a design involving two pluggable "ESIS-handlers", one
> "low-level", where GI's, attribute names, attribute values, comments etc
> points directly into the source. (typically via a filemapping or an
> The "low-level" ESIS-handler may copy the data into "real" strings,
> concatenate the consecutive PCDATA sections , build the tree, do
> etc and pass the events to an optional "higher-level" ESIS-handler.
> I think/hope the layer which triggers the low-level events won't be very
> different from Mr Clark's "quick and dirty" parser.
> (Not sure yet whether the low-level handler should just receive events, or
> whether it should query for the next event/token.)
> xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
> Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
> To (un)subscribe, mailto:email@example.com the following message;
> (un)subscribe xml-dev
> To subscribe to the digests, mailto:firstname.lastname@example.org the following
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:email@example.com)
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)