... Yep, and back up and describe the situation that you think demands such a solution in the first place. MaxMessage 1 of 4 , Nov 1, 2002View Source
> As far as I am aware the most realistic solution is simplyYep, and back up and describe the situation that you think demands such
> to avoid using CDATA sections in the SVG/XML document that
> you plan to treat in the way you suggest.
a solution in the first place.
... Believe it or not, I missed this whole thread. Sorry! ... You can replace ]] with something like ]] ]] . Ugly? You betcha! Paul PrescodMessage 1 of 4 , Nov 8, 2002View Sourcewesleytperkins wrote:
> This is a question I posted earlier which did not receive anyBelieve it or not, I missed this whole thread. Sorry!
> satisfactory answer. Given the accumulation of XML talent in this
> newsgroup I am trying again:
> ...You can replace "]]>" with something like "]]>]]<![CDATA[>". Ugly? You
> I would like to include the entire text of one SVG file as unparsed
> content in in another SVG file -- possibly as the text content of a
> <desc> element or a custom element. An obvious way to do this is to
> use a CDATA section to mark the included text as unparsed content.
> However this will not work if the included text also contains CDATA
> sections, since these can not be nested:
> This must be a common XML problem and I'm curious if there is some
> recommended solution. One non-general solution would be to replace
> internal CDEnd tokens ']]>' by an unusual combination of characters.
> A more general solution would be to encode the entire contents.
> Does anyone have a favorite idiom to deal with this sort of thing?