commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Fortner <>
Subject Re: [compress] Some merging in zip package
Date Tue, 10 Feb 2009 17:06:53 GMT
I meant specifically if I was using this library at both ends of the
equation.  I assume that if you use different tools at either end, you may
have some challenges.  But if I use this library at both ends, and use the
default settings, then I imagine I would have some difficulty on the
decompression side.  I think Linux may default to the UTF-8 encoding, and
Windows to the ISO-8859-1 encoding.


On Tue, Feb 10, 2009 at 8:57 AM, Stefan Bodewig <> wrote:

> On 2009-02-10, Mark Fortner <> wrote:
> >>> ZipArchiveOutputStream will now use the platform's native encoding
> >>> instead of UTF8 by default now, while JarArchiveOutputStream
> >>> explicitly sets the encoding to UTF8.  Does anybody consider this a
> >>> problem?
> > What happens if you try to take a file that was created on a machine with
> > one default encoding, and send it to another machine with a different
> > default encoding (i.e. Linux  -> Windows)?
> It depends on what you use to extract the archive, I guess.  In a
> situation like this you are much better off specifiying the encoding
> explicitly.
> Most tools don't assume UTF-8 (the old default) at all, so you
> wouldn't be able to extract an archive created by the jar command (or
> the prevision version of ZipArchiveOutputStream) in a scenario like
> this either.
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Mark Fortner


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