• To: "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: "Karl Waclawek" <karl@w...>
• Date: Mon, 31 Mar 2003 16:44:07 -0500
• References: <r01050400-1024-7F4CF33F63BE11D7B1500003937A08C2@[192.168.124.11]>

> 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.

OK, I understand. No, that is not easily possible.

You could try this (not tested):
Clear the characterDataHandler in the startCDATASectionHandler,
then set a defaultHandler, getting the raw (but encoded) data + do your
own processing on them, and finally re-set everything in the
endCDATASectionHandler. That is problematic especially when you
have entity references, although it is possible to have them expanded.

Karl

• References:
  • Re: If XML is too hard for a programmer, perhaps he'd b e better off as a crossing guard
    • From: "Simon St.Laurent" <simonstl@s...>

• Prev by Date: Re: If XML is too hard for a programmer, perhaps he'd b e better off as a crossing guard
• Next by Date: XML sometimes takes programming (was crossing guard)
• Previous by thread: XML sometimes takes programming (was crossing guard)
• 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