See the zip 3 manual
page for more information.) This will definitely be corrected in the
next major release.
Archives read from standard input are not yet supported, except with
funzip (and then only the first member of the archive can be extracted).
Archives encrypted with 8‐bit passwords (e.g., passwords with accented
European characters) may not be portable across systems and/or other
archivers. See the discussion in DECRYPTION above.
unzip’s -M (‘‘more’’) option tries to take into account automatic wrap‐
ping of long lines. However, the code may fail to detect the correct
wrapping locations. First, TAB characters (and similar control se‐
quences) are not taken into account, they are handled as ordinary print‐
able characters. Second, depending on the actual system / OS port, un‐
zip may not detect the true screen geometry but rather rely on "commonly
used" default dimensions. The correct handling of tabs would require
the implementation of a query for the actual tabulator setup on the out‐
put console.
Dates, times and permissions of stored directories are not restored ex‐
cept under Unix. (On Windows NT and successors, timestamps are now re‐
stored.)
[MS‐DOS] When extracting or testing files from an archive on a defective
floppy diskette, if the ‘‘Fail’’ option is chosen from DOS’s ‘‘Abort,
Retry, Fail?’’ message, older versions of unzip may hang the system, re‐
quiring a reboot. This problem appears to be fixed, but control‐C (or
control‐Break) can still be used to terminate unzip.
Under DEC Ultrix, unzip would sometimes fail on long zipfiles (bad CRC,
not always reproducible). This was apparently due either to a hardware
bug (cache memory) or an operating system bug (improper handling of page
faults?). Since Ultrix has been abandoned in favor of Digital Unix
(OSF/1), this may not be an issue anymore.
[Unix] Unix special files such as FIFO buffers (named pipes), block de‐
vices and character devices are not restored even if they are somehow
represented in the zipfile, nor are hard‐linked files relinked. Basi‐
cally the only file types restored by unzip are regular files, directo‐
ries and symbolic (soft) links.
[OS/2] Extended attributes for existing directories are only updated if
the -o (‘‘overwrite all’’) option is given. This is a limitation of the
operating system; because directories only have a creation time associ‐
ated with them, unzip has no way to determine whether the stored attrib‐
utes are newer or older than those on disk. In practice this may mean a
two‐pass approach is required: first unpack the archive normally (with
or without freshening/updating existing files), then overwrite just the
directory entries (e.g., ‘‘unzip ‐o foo */’’).
[VMS] When extracting to another directory, only the [.foo] syntax is
accepted for the -d option; the simple Unix foo syntax is silently ig‐
nored (as is the less common VMS foo.dir syntax).
[VMS] When the file being extracted already exists, unzip’s query only
allows skipping, overwriting or renaming; there should additionally be a
choice for creating a new version of the file. In fact, the ‘‘over‐
write’’ choice does