>How can the CDATA ending delimiter "]]>" be represented within a CDATA
>section itself?

> How can the CDATA ending delimiter "]]>" be represented within a CDATA
> section itself?
>
> Consider an XML document that is intended to contain an embedded,
> uninterpreted XML example. Generally, the easiest way to represent it
would
> be to put the embedded XML example inside a CDATA section. But if the
> example has a CDATA section itself, then the ending delimiter will be
> interpreted as the end of the "real" CDATA section. Here's even a simpler
> example with a script's conditional statement:
>
> <test>
> <!CDATA[
> ...
> if g[a[i]]>f ...
> ...
> ]]>
> </test>
>
> This element returns errors when viewed and/or validated in VS.Net and IE
6.
> They both interpret the "]]>" within the "if g[a[i]]>f ..." statement as
the
> end of the CDATA section. Multiple SGML sources on the web indicate that
> the above XML should process correctly without change. Others say that
the
> ">" (greater than) should be escaped inside the CDATA section using the
> entity reference &gt;. For example:
>
> <test>
> <!CDATA[
> ...
> if g[a[i]]&gt;f ...
> ...
> ]]>
> </test>
>
> But this doesn't work either because entity references are not interpreted
> within a CDATA section. That's the whole point of the CDATA section... to
> represent literal character data without escapes.
>
> Is it even possible then? Or is this just a bug in all MS XML parsers?
>
>

Cade Perkins wrote:
> How can the CDATA ending delimiter "]]>" be represented within a CDATA
> section itself?
> ...

> Just don't use CDATA as well. Simply escape all "<" as "&lt;" and you're
> done.

"Rowland Shaw" <spamfilter@anotherpointless.org> wrote in message
news:OOhnPmwuDHA.2136@TK2MSFTNGP10.phx.gbl...
> Two options:
> <test>
> <![CDATA[
> ...
> if g[a[i]]>]]&gt;<![CDATA[f ...
> ...
> ]]>
> </test>
>
> And the more readable:
> <test>
> <![CDATA[
> ...
> if g[a[i]] > f ...
> ...
> ]]>
> </test>
>

"Cade Perkins" <msnews@perkcan.net> wrote in message
news:Or4p5D2uDHA.3144@tk2msftngp13.phx.gbl...
> Julian F. Reschke said:
> > Just don't use CDATA as well. Simply escape all "<" as "&lt;" and you're
> > done.
>
> Thanks for the help! This doesn't work for me in my case, but other
> responses help me find a reasonable solution. For a few characters, this
> fix would be fine, but if I am automating the process and simply want to
> store a block of unknown text data, I don't want to have to consider and
> replace every possible meta character that I need to escape using entity
> references. The CDATA solution would work great except for the inability
to
> escape the end delimiter. I'm surprised that it is not part of the
> specification. I don't understand all the roots of SGML and I imagine it
> has an explanation, but every other language/specification I've worked
with
> allows some way of escaping the delimiter.
>