Re: [compress] Some merging in zip package

2009-02-11 Thread Stefan Bodewig
On 2009-02-11, Torsten Curdt tcu...@apache.org wrote: I am also not so sure this really all that bad. I guess there are 3 scenarios 1: the archive standard is known to use a specific encoding 2: the encoding is specified inside the archive (which is similar to 1) 3: we have no clue about the

Re: [compress] Some merging in zip package

2009-02-11 Thread sebb
On 11/02/2009, Stefan Bodewig bode...@apache.org wrote: On 2009-02-11, Torsten Curdt tcu...@apache.org wrote: I am also not so sure this really all that bad. I guess there are 3 scenarios 1: the archive standard is known to use a specific encoding 2: the encoding is specified inside

Re: [compress] Some merging in zip package

2009-02-11 Thread Stefan Bodewig
On 2009-02-11, sebb seb...@gmail.com wrote: That seems likely to produce some confusion - would it not be better to default to UTF-8? Yes, that's been my initial question. Is it OK to have no default at all or should we keep with UTF-8? Given that ZipArchiveInputStream doesn't support

[compress] Some merging in zip package

2009-02-07 Thread Stefan Bodewig
Hi, I've merged ZipEntry into ZipArchiveEntry and ZipOutputStream into ZipArchiveOutputStream. As a side effect ZipArchiveOutputStream now supports encoding of file names and the zip file comment (among other things that it does better than java.util.zip.ZipOutputStream like providing usable