|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: identity transform - include CDATA's, etc
the reason I wanted the <![CDATA[]]> to come out in the output is that output of the identity transform is supposed to undergo another xslt transform.
if my testing is correct. And this is where the problem is. if the identity transform outputs: <a>b<a> this is fine, but if it outputs: <a>b</a> this is not, as it could obviously run into problems when the '<' signs aren't xml but something else (eg javascript code). in this case, the source document would be valid xml b/c of the CDATA beginning and end markers, but the output would not be. I tested saxon and msxsl using the identity transform on jscript.xml: <?xml version="1.0" encoding="utf-8"?> <docroot> <a> <![CDATA[ if( x < y ) alert(); ]]> </a> </docroot> and it output: <?xml version="1.0" encoding="utf-8"?> <docroot> <a> if( x < y ) alert(); </a> </docroot> so this would be good if this is the way '<' signs in CDATA sections are always handled, and if this behavior is reliable and predictable. but is it, in fact, reliable across the multitude of xslt processors and other circumstances? Is it part of the xslt spec? I had understood that other behaviors similar to this one are not reliable. _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








