DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29046>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29046 Encoding attribute is not returning properly in output XML header ------- Additional Comments From [EMAIL PROTECTED] 2004-05-17 21:11 ------- -The XML property of the DOMDocument obj is not returning the encoding attributes for the output XML data correctly, except for the pre-defined encoding names. I have found that There is a function named: XalanTranscodingServices::makeNewTranscoder(..) In …/src/xalanc/PlatformSupport/XalanTranscodingServices.hpp which is supposed to make a new transcoder for the new desired output encodings. It is working with xslt (xalan with icu version), but it is not working with Xalan properly. -With Xalan-C1.8, while running the conformance test on output bucket on Solaris_27-cc_62, I got the following extra failings. The problem is that the following stylesheets can not be transformed properly with the desired encoding attributes. In the result XML data all the encoding names changed to the default UTF-8 instead: output20.xsl output21.xsl output23.xsl -Besides conf I tried to run these testcases using SimpleTransform sample program, and even manually using Xalan.exe, and they all failed again with the same results. Even when I used –e option to force the encoding with Xalan.exe, again it transformed the encoding attribute to default UTF-8. I got the same results with Xalan-C1.7 and on AIX 5.1, Linux 7.2, and HP-UX 11. -I ran the test cases with xslt4c1.7 executables, and it transformed the encoding attributes correctly. Java test harness couldn’t detect these extra failures for Xalan-C1.7 and Xalan-C1.8 on unix platforms either. The encoding names that cannot be transformed correctly are: -encoding= SHIFT_JIS is used in output73.xsl (encoding on HTML output), output20.xsl (encoding on xml output), it is supposed not to fail on HTML output, but is not working on xml output either. -encoding= BIG5 is used just in output21.xsl -encoding=ISO-2022-JP is used just in output23.xsl None of the other test buckets are using encoding attributes with the above encoding names, and there is no problem with the pre-defined encoding names. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
