• To: "'Karl Waclawek'" <karl@w...>,"'Simon St.Laurent'" <simonstl@s...>,<xml-dev@l...>
• Subject: RE: If XML is too hard for a programmer, perhaps he'd b e better off as a crossing guard
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Tue, 1 Apr 2003 09:32:36 +0100
• Importance: Normal
• In-reply-to: <002e01c2f7ce$ab3d2530$9e539696@citkwaclaww2k>
• Reply-to: <michael.h.kay@n...>

> > No, I'm saying that it doesn't provide any way for me to 
> say "please 
> > don't process the contents of this CDATA section as text; please 
> > process it as if the CDATA section wasn't there."
> >
> <snip/>
> > 
> > I'm not interested in suppressing the event, but rather on 
> suppressing 
> > its effect on the parser.
> 

If speed of development is more important to you than speed of
execution, you can handle this kind of document in Saxon by using the
saxon:parse() extension function from within a stylesheet to parse the
text nodes in which the markup was escaped - so long as you know which
these are.

Michael Kay

• Prev by Date: Re: If XML is too hard for regular expressions, perhaps he'dbe better off with a parser
• Next by Date: RE: If XML is too hard for a programmer, perhaps he'd b e better off as a crossing guard
• Previous by thread: Re: If XML is too hard for regular expressions, perhaps he'd be better off with a parser
• Next by thread: RE: If XML is too hard for a programmer, perhaps he'd b e better off as a crossing guard
• Index(es):
  • Date
  • Thread