 |
|
|
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@xxxxxxxxxxxxxx> 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 !!!
>
>
--
Vasu Chakkera
Numerical Algorithms Group Ltd.
Oxford
www.vasucv.com
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
