[ http://issues.apache.org/jira/browse/XALANJ-2087?page=all ]

Brian Minchau updated XALANJ-2087:
----------------------------------

    Attachment: serializer.jira.2087.patch1.txt

Elliotte Rusty Harold: There is a new method in EncodingInfo.java, private 
static boolean inEncoding(char ch, byte[] data);
  I'd appreciate if you had a look at it. It has your suggestions for work 
arounds for Japanese encoding bugs,
  but they are commented out for now. Please review and make sure I've got the 
logic right (and not reversed my true/false).

Sergey Ushakov: Thanks for you attachements to this issue. Unfortunately we 
can't have a build or runtime dependency on 1.4.  Perhaps with enough reflection
 we could make your contribution work.  I certainly like it because it uses 1.4 
methods exactly for the right purpose.  My patch uses String.getBytes(encoding),
 which has undefined behavior when the chars are not in the encoding.

> Get rid of the dependency on sun.io.CharToByteConverter
> -------------------------------------------------------
>
>          Key: XALANJ-2087
>          URL: http://issues.apache.org/jira/browse/XALANJ-2087
>      Project: XalanJ2
>         Type: Improvement
>   Components: Xalan
>     Versions: CurrentCVS
>     Reporter: Jack
>     Assignee: Brian Minchau
>  Attachments: Converter.java, Encodings&Converter.zip, 
> serializer.jira.2087.patch1.txt
>
> The class org.apache.xml.serializer.Encodings references 
> sun.io.CharToByteConverter directly, while the latter is not a public API. Is 
> it possible to use java.nio.charset classes instead to remove this dependency?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to