commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (Commented) (JIRA)" <>
Subject [jira] [Commented] (COMPRESS-176) ArchiveInputStream#getNextEntry(): Problems with WinZip directories with Umlauts
Date Fri, 24 Feb 2012 16:48:49 GMT


Sebb commented on COMPRESS-176:

The plain names use / and look OK when using CP437.

For some odd reason, the unicode extra fields use \ instead of /
I think that may be a Winzip bug - it does not make sense to use a different separator for
the extra fields.

To confirm this is a bug, it would be useful to see how other zip tools use the extra fields
- are there any?
Apart from Ant or other code based on Commons Compress, of course!

Alternatively, find some documentation as to the correct contents of the field.

My version of Winzip is too old to support the fields; if you have purchased a more recent
one perhaps you could e-mail their support desk?

A possible work-round would be to make the \ => / behaviour optional; I agree we should
not do this by default
> ArchiveInputStream#getNextEntry(): Problems with WinZip directories with Umlauts
> --------------------------------------------------------------------------------
>                 Key: COMPRESS-176
>                 URL:
>             Project: Commons Compress
>          Issue Type: Bug
>          Components: Archivers
>    Affects Versions: 1.3
>         Environment: Windows 7
>            Reporter: Wurstbrot mit Senf
>         Attachments:,,
> There is a problem when handling a WinZip-created zip with Umlauts in directories.
> I'm accessing a zip file created with WinZip containing a directory with an umlaut ("รค")
with ArchiveInputStream. When creating the zip file the unicode-flag of winzip had been active.
> The following problem occurs when accessing the entries of the zip:
> the ArchiveEntry for a directory containing an umlaut is not marked as a directory and
the file names for the directory and all files contained in that directory contain backslashes
instead of slashes (i.e. completely different to all other files in directories with no umlaut
in their path).
> There is no difference when letting the ArchiveStreamFactory decide which ArchiveInputStream
to create or when using the ZipArchiveInputStream constructor with the correct encoding (I've
tried different encodings CP437, CP850, ISO-8859-15, but still the problem persisted).
> This problem does not occur when using the very same zip file but compressed by 7zip
or the built-in Windows 7 zip functionality.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message