You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/12/09 19:38:47 UTC
DO NOT REPLY [Bug 15190] New: -
SJIS encoding not supported
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15190>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15190
SJIS encoding not supported
Summary: SJIS encoding not supported
Product: XalanJ2
Version: 2.2.x
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Enhancement
Priority: Other
Component: org.apache.xalan
AssignedTo: xalan-dev@xml.apache.org
ReportedBy: graeme.st.clair@hds.com
JDK 1.4.1_01. I've tried both the built-in xalan (2.2.D11), and (if I got it
right) the "endorsed", and both say SJIS is not supported as an encoding for an
input XML document. I removed any 'encoding' from the xsl:output element.
In the case of the built-in, this happens whether I do the transform from the
W2K cmd line, or from inside my Java app. (Alas, I don't know how to invoke a
different xalan from inside a Java app.)
Is there an intention to support this encoding, or am I doing something wrong?
I'm not attaching any material, because the question looks like it has a
straight yes or no answer...