[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Truncation parsing <

• To: craig@z..., Mike Brown <mike@s...>
• Subject: Re: Truncation parsing &lt;
• From: Eric Bohlman <ebohlman@e...>
• Date: Mon, 05 Aug 2002 01:12:58 -0500
• Cc: xml-dev@l...
• In-reply-to: <200208021754.g72HsrTl070023@c...>
• Organization: OMS Development

8/2/02 12:54:53 PM, Mike Brown <mike@s...> wrote:

>Although you know the element contains a single string of character data,
>'Shipping Address (< 31)', a parser, acting on the lexical constructs it
>encounters, is likely, though not required, to report this as 3 calls to
>characters() in the case of SAX, or as 3 adjacent text nodes in the case of
>DOM. This is normal behavior. In SAX you just have to live with it. In DOM you
>may have the option of normalizing the text beforehand; check the DOM specs
>and docs for your parser.

Correct in the case of SAX; the spec explicitly says that characters() may deliver its results in 
chunks.  Incorrect in the case of DOM; the spec says that a parser must represent contiguous text as 
a single node when creating a DOM and that adjacent text nodes in a DOM can only arise out of 
subsequent manipulation. 

• References:
  • Re: Truncation parsing &lt;
    • From: Mike Brown <mike@s...>

• Prev by Date: Re: Re: maps
• Next by Date: Re: Please no UOM (was Re: maps)
• Previous by thread: Re: Truncation parsing &lt;
• Next by thread: Re: Truncation parsing &lt;
• Index(es):
  • Date
  • Thread