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 Thu Aug 9 12:26:12 2001
--- shadow/3047.tmp.20791 Thu Aug 9 12:39:01 2001
***************
*** 93,95 ****
--- 93,108 ----
We ran another test and we still get 0xFC in the output (invalid XML with UTF-8
encoding). So your test suggest that this was fixed with the most recent
release. What would be the best way for us to verify that?
+
+ ------- Additional Comments From [EMAIL PROTECTED] 2001-08-09 12:39 -------
+ btw, here's what we get when trying to validate the output file.
+
+ ========= Parsing file:/tmp/031.xml ==========
+ file:/tmp/031.xml; Line 44; Column 42
+ XSL Error: Could not parse file:/tmp/031.xml document!
+ XSL Error: SAX Exception
+ XSLT: An invalid XML character (Unicode: 0xfc) was found in the element
+ content of the document.
+ Xalan: was not successful.
+ XSLProcessor: done
+
