commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damjan Jovanovic <damjan....@gmail.com>
Subject Re: UTF8 filename issue with TarOutputStream
Date Sun, 02 Sep 2012 16:38:44 GMT
The test on http://jira.codehaus.org/browse/MASSEMBLY-515
Succeeds with ?'s instead of non-ASCII characters on commons-compress-1.0
Succeeds with the correct characters on commons-compress-1.4.1

Why is there 2 projects? Why don't Maven and Ant use commons-compress?

Damjan

On Sun, Sep 2, 2012 at 1:45 PM, Gary Gregory <GGregory@rocketsoftware.com>wrote:

> I wonder if [compress] has the same issue?
>
> Gary
>
> Begin forwarded message:
>
> From: falcon sheep <falcon.sheep@gmail.com<mailto:falcon.sheep@gmail.com>>
> Date: September 2, 2012 5:26:07 EDT
> To: <user@ant.apache.org<mailto:user@ant.apache.org>>
> Subject: UTF8 filename issue with TarOutputStream
> Reply-To: Ant Users List <user@ant.apache.org<mailto:user@ant.apache.org>>
>
> Hi,
>
> I have raised a bug with TarOutputStream when a TAR file is being written,
> and:
> 1. One or more filenames are so long that they require GNU mode
> 2. The platform encoding is UTF-8
> 3. Any character in a long filename results in a multibyte UTF-8 sequence
>
> an exception is thrown:
> "Problem creating TAR: request to write 'xxx' bytes exceeds size in header
> of 'xxx' bytes"
>
> the same has been discussed and solved in:
> http://jira.codehaus.org/browse/PLXCOMP-195
>
> with the patch applied as well
>
> bug id:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=53811
>
> is there any chance of solving them in the next release.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message