Hi Steve, Yes, if you've loaded your XML as a DOM Variable, then outputting causes the Witango XML Parser to "consume" the CDATA definition. The exact reason why this happens is not clear, because this behavior is not seen in more modern parsers when printing a finished DOM.
You could try doubling up the CDATA sections. I think I tried that once, and can't remember the results. Otherwise, just "write" the output as XML "text" - you typically only need the XML as a DOM Variable if you have to manipulate the content. As well, technically the absence of the CDATA does not necessary mean the content is invalid. Most XML parsers that will consume your content shouldn't have a problem with what you have, unless you're expecting some value that could break the XML - in which case, then you can just encode the characters. Does that make any sense? Let us know...... > -----Original Message----- > From: Steve Kevill [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 25, 2004 1:29 PM > To: [EMAIL PROTECTED] > Subject: RE: Witango-Talk: Witango/XML and CDATA... > > Scott, > > I will take a look at your reply. Just to clarify, this is > an example > of what I'm doing: > > <@ASSIGN request$xml '<@DOM VALUE=" > <myXml> > <code><![CDATA[<font > size='+1'>@@request$myVariable</font>]]></code> > </myXml> > ">'> > > Then outputting the data by changing the header info. The > output looks > like this: > > <myXml> > <code><font size='+1'>Variable contents...</font></code> > </myXml> > > I need it to look like this: > > <myXml> > <code><![CDATA[<font size='+1'>Variable > contents...</font>]]></code> > </myXml> > > Thanks, > > Steve Kevill > > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
