[ http://issues.apache.org/jira/browse/LANG-100?page=all ]
     
Henri Yandell resolved LANG-100:
--------------------------------

    Resolution: Fixed

Fixed for high/low I believe, but private high get skipped currently.

svn ci -m "Adding a test and a fix for LANG-100. This is a bug in which the 
randomly created String can some
times be illegal unicode; because the code does not consider when relationships 
exist between characters. High and low surrogates are now dealt with, but I'm 
skipping private high surrogates because I can't find out what to do. Need to 
go plod very slowly through the spec. This site was very useful: 
http://www.alanwood.net/unicode/private_use_high_surrogates.html"; 
src/*/org/apache/commons/lang/Random*

Sending        src/java/org/apache/commons/lang/RandomStringUtils.java
Sending        src/test/org/apache/commons/lang/RandomStringUtilsTest.java
Transmitting file data ..
Committed revision 417319.

> [lang] RandomStringUtils.random() family of methods create invalid unicode 
> sequences
> ------------------------------------------------------------------------------------
>
>          Key: LANG-100
>          URL: http://issues.apache.org/jira/browse/LANG-100
>      Project: Commons Lang
>         Type: Bug

>     Versions: 2.1
>  Environment: Operating System: All
> Platform: All
>     Reporter: Stefan Höhne
>      Fix For: 2.2

>
> Problem are surrogate pairs: 
> E.g. RandomStringUtils.random(int) may create strings with a high surrogate 
> not
> followed by a low surrogate character.
> When processing them, we get errors in string-conversion-functions later on.

-- 
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