[
https://issues.apache.org/jira/browse/COMPRESS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895379#action_12895379
]
Stefan Bodewig commented on COMPRESS-114:
-----------------------------------------
A snapshot I compiled myself can be found at
http://people.apache.org/~bodewig/commons-compress-1.1-SNAPSHOT.jar and I'll
remove it once 1.1 has been released.
The unit tests pass for me on my Ubuntu system and it's pretty likely it is
more of an environment setting thing. I may also note that the tests pass in
the Apache Gump builds both on Linux (Ubuntu 8.4) and Solaris 10.
Returning to the original problem, commons-compress really doesn't implement
POSIX tar or even comes close to it. It mostly lives at the least common
denominator of all tar dialects, ustar. And this means the only characters
that are really supported come from the seven bit ASCII set - with anything
else you can only hope it works.
> 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.