[jruby-dev] [jira] Created: (JRUBY-4641) Regression: JRuby can't handle non-ascii characters correctly

[Yoko Harada (JIRA)]

Regression: JRuby can't handle non-ascii characters correctly
-------------------------------------------------------------

                 Key: JRUBY-4641
                 URL: http://jira.codehaus.org/browse/JRUBY-4641
             Project: JRuby
          Issue Type: Bug
          Components: Core Classes/Modules
    Affects Versions: JRuby 1.5
            Reporter: Yoko Harada


Since this commit:
{noformat} 
6323269fcfb2341ff8fa3b198037e1290982926 is the first bad commit
commit 26323269fcfb2341ff8fa3b198037e1290982926
Author: Charles Oliver Nutter <head...@headius.com>
Date:   Wed Mar 10 16:21:23 2010 -0600

    Fixes for JRUBY-4553: Scalability: JRuby suffers from Java Charset lock 
contention

:040000 040000 90fadcf6d377b3f16b3ee78ff2616e4786137af3 
1cede90a93f6e2410aba6603df3552c0d
4fef5d7 M      src
{noformat} 

JRuby can't handle non-ascii characters correctly. Because of this regression, 
some of embedding API test cases failed. For example,

{noformat} 
expected:<[&#12356;&#12369;&#12390;&#12427;&#12397;! &#65310;&#12288;]JRuby> 
but was:<[?????! ??]JRuby>

expected:<"R[ésumé]"> but was:<"R[&#65533;sum\351]">
{noformat} 
As far as I remember, "bytes = script.getBytes();" in each exception handling 
block was used to get bytes before. After the commit, the block was gone. 
Maybe, this would be the reason.


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



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email