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=3047 *** shadow/3047 Wed Aug 8 10:01:32 2001 --- shadow/3047.tmp.6090 Wed Aug 8 10:01:32 2001 *************** *** 0 **** --- 1,29 ---- + +============================================================================+ + | Xalan failing to escape non UTF-8 characters | + +----------------------------------------------------------------------------+ + | Bug #: 3047 Product: XalanJ2 | + | Status: NEW Version: 2.1.0 | + | Resolution: Platform: Sun | + | Severity: Major OS/Version: Solaris | + | Priority: Other Component: Xalan | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + When specifying UTF-8 in the XSL, Xalan fails to escape any non UTF-8 + chracters. For example: + + Source XML contains: Michael Stürmer (in case this is translated, I + entered the numeric value 252). + XSL contains: <xsl:output method="xml" encoding="UTF-8"/> + Output file contains: Michael Stürmer (ü is an invalid character) + Output should contain: Michael Stürmer (in case this is translated, I + entered the numeric value 252). + + When specifying us-ascii as the encoding in the xsl it works, but this solution + is not very popular. + Is there a fix to this? \ No newline at end of file
