Re: xml/ada dropping data when pre-defined entities are separated by space?

["björn lundin" <b.f.lundin@gmail.com>]

On 31 Jan, 15:56, Emmanuel Briot <briot.emman...@gmail.com> wrote:
> > I was just going to ask what makes xml/ada decide why a textnode is
> > sometimes split into several nodes. I see the pattern now, of course,
> > 'split on predefined entity' but why?
>
> Because XML/Ada tries to be as efficient as possible, and normalizing
> the document takes time that a lot of application have no need for. If
> indeed your application is only able to deal with normalized document
> (it really shouldn't, the XML standard is quite clear that a document
> is not necessarily normalized), then indeed you should call Normalize.

Ok. A colleauge of mine pointed me to
http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1312295772
which states :
"When a document is first made available via the DOM, there is only
one Text node for each block of text. Users may create adjacent Text
nodes that represent the contents of a given element without any
intervening markup, but should be aware that there is no way to
represent the separations between these nodes in XML or HTML, so they
will not (in general) persist between DOM editing sessions. The
normalize() method on Node merges any such adjacent Text objects into
a single node for each block of text."

Isn't this the case of the first sentence?
I parse the document, I do not edit it in any way,
I traverse it, and there are several childnodes instead of one.

Or how should 'When a document is first made available via the DOM'
be interpreted?

/Björn