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

Re: Truncation parsing <

• To: craig@z...
• Subject: Re: Truncation parsing <
• From: Mike Brown <mike@s...>
• Date: Fri, 2 Aug 2002 11:54:53 -0600 (MDT)
• Cc: xml-dev@l...
• In-reply-to: <33501.172.16.0.181.1028300737.squirrel@m...>"from Craig H Fry at Aug 2, 2002 11:05:37 am"

Craig H Fry wrote:
> I am having a problem with truncation when trying to parse an element that
> contains <
> I can recreate the problem with & and > also
> 
> Here is a sample of what I am parsing
> 
> <element>Shipping Address (&lt; 31)</element>
> 
> When parsed, all I get is 31)

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.

   - Mike
____________________________________________________________________________
  mike j. brown                   |  xml/xslt: http://skew.org/xml/
  denver/boulder, colorado, usa   |  resume: http://skew.org/~mike/resume/

• Follow-Ups:
  • Re: Truncation parsing &lt;
    • From: Eric Bohlman <ebohlman@e...>

• References:
  • Truncation parsing &lt;
    • From: "Craig H Fry" <craig@z...>

• Prev by Date: Re: Re: URIs, concrete (was Re: Un-ask the
• Next by Date: Re: Keeping ISO 8879 Alive (was RE: Markupperspective not code)
• Previous by thread: Truncation parsing &lt;
• Next by thread: Re: Truncation parsing &lt;
• Index(es):
  • Date
  • Thread