PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3583 *** shadow/3583 Thu Sep 13 06:10:43 2001 --- shadow/3583.tmp.3268 Thu Sep 13 06:10:43 2001 *************** *** 0 **** --- 1,37 ---- + +============================================================================+ + | HTML Output escaped in certain circumstances the characters < and & but sh | + +----------------------------------------------------------------------------+ + | Bug #: 3583 Product: XalanJ2 | + | Status: NEW Version: 2.2.x | + | Resolution: Platform: PC | + | Severity: Normal OS/Version: Windows NT/2K | + | Priority: Other Component: org.apache.xalan | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + When the output method is declared as "html", the content of <script> elements + should not be escaped (according to Section 16.2 of the XSLT 1.0 spec.) + But in certain cirumstances the characters < and & are escaped to < and & + + This version of an XSLT template is working correctly: + <script> if (a < b) foo() </script> + and the ouput is: + <script> if (a < b) foo() </script> + + + But if you use the 'if statement' within another tag the < is still escaped: + <script> <myNode> if (a < b) foo()> </myNode> </script> + + ===> produce following output and not the same like in the example above: + <script> <myNode> if (a < b) foo() </myNode> </script> + + + I tested this with Xalan version xalan-j_2_0_1 and with xalan-j_2_2_D10. Both + show the decribed behavoir. I tested it with other XSLT parser (SAXON, MSXSLT, + EXCELON) and it works like expected. + of others XSLT processors and it is working (except XT).
