[jira] Issue Comment Edited: (COMPRESS-114) TarUtils.parseName does not properly handle characters outside the range 0-127

["Pavel (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COMPRESS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895204#action_12895204 ] 

Pavel edited comment on COMPRESS-114 at 8/4/10 6:38 AM:
--------------------------------------------------------

Hello,


I've checked out the trunk from http://svn.apache.org/repos/asf/commons/proper/compress and run the testRoundTripNames() test from TarUtilsTest. It failed (the last checkName() call with spec. characters). The test was performed on Ubuntu 8.10.

Has the fix been tested on Linux? In which version can find the final fix to this special characters problem?

Thanks





      was (Author: partysan):
    Hello,


I've checked out the trunk from http://svn.apache.org/repos/asf/commons/proper/compress and run the testRoundTripNames() test from TarUtilsTest. It failed (the last checkName() call with spec. characters). The test was performed on Ubuntu 8.10.






  
> TarUtils.parseName does not properly handle characters outside the range 0-127
> ------------------------------------------------------------------------------
>
>                 Key: COMPRESS-114
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-114
>             Project: Commons Compress
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: Windows/Suse
>            Reporter: Helmut M.
>             Fix For: 1.1
>
>         Attachments: plusMinusForJIRAwithLicense.tar, TarArchiveEntry.java, TarArchiveInputStream.java, TarUtils.java
>
>
> if a tarfile contains files with special characters, the names of the tar entries are wrong.
> example:
> correct name: 0302-0601-3±±±F06±W220±ZB±LALALA±±±±±±±±±±CAN±±DC±±±04±060302±MOE.model
> name resolved by TarUtils.parseName: 0302-0101-3ﾱﾱﾱF06ﾱW220ﾱZBﾱHECKMODULﾱﾱﾱﾱﾱﾱﾱﾱﾱﾱECEﾱﾱDCﾱﾱﾱ07ﾱ060302ﾱDOERN.model
> please use: 
> result.append(new String(new byte[] { buffer[i] }));
> instead of: 
> result.append((char) buffer[i]);
> to solve this encoding problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.