while you got what you wanted, as other suggested, you must answer for
yourself, why you need CDATA in the output. Probably worth doing a
design check on your application. Workarounds normally bite you later
..
On 06/01/2009, J. S. Rawat <jrawat(_at_)aptaracorp(_dot_)com> wrote:
At 03:11 PM 1/6/2009, Michael Kay wrote:
One way is to use cdata-section-elements on xsl:output as
suggested already on this thread, another is to generate the CDATA start
and
end strings (<![CDATA[ and ]]>) using character maps or
disable-output-escaping.
Thanks Michael Kay, this is what I was looking for !!!
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--
Vasu Chakkera
Numerical Algorithms Group Ltd.
Oxford
www.vasucv.com
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--