be
stored in the archive, and possibly a summary when finished with
each archive. The -q[q] options suppress the printing of some or
all of these messages.
-s [OS/2, NT, MS‐DOS] convert spaces in filenames to underscores.
Since all PC operating systems allow spaces in filenames, unzip
by default extracts filenames with spaces intact (e.g.,
‘‘EA DATA. SF’’). This can be awkward, however, since MS‐DOS in
particular does not gracefully support spaces in filenames. Con‐
version of spaces to underscores can eliminate the awkwardness in
some cases.
-S [VMS] convert text files (-a, -aa) into Stream_LF record format,
instead of the text‐file default, variable‐length record format.
(Stream_LF is the default record format of VMS unzip. It is ap‐
plied unless conversion (-a, -aa and/or -b, -bb) is requested or
a VMS‐specific entry is processed.)
-U [UNICODE_SUPPORT only] modify or disable UTF‐8 handling. When
UNICODE_SUPPORT is available, the option -U forces unzip to es‐
cape all non‐ASCII characters from UTF‐8 coded filenames as
‘‘#Uxxxx’’ (for UCS‐2 characters, or ‘‘#Lxxxxxx’’ for unicode
codepoints needing 3 octets). This option is mainly provided for
debugging purpose when the fairly new UTF‐8 support is suspected
to mangle up extracted filenames.
The option -UU allows to entirely disable the recognition of
UTF‐8 encoded filenames. The handling of filename codings within
unzip falls back to the behaviour of previous versions.
[old, obsolete usage] leave filenames uppercase if created under
MS‐DOS, VMS, etc. See -L above.
-V retain (VMS) file version numbers. VMS files can be stored with
a version number, in the format file.ext;##. By default the
‘‘;##’’ version numbers are stripped, but this option allows them
to be retained. (On file systems that limit filenames to partic‐
ularly short lengths, the version numbers may be truncated or
stripped regardless of this option.)
-W [only when WILD_STOP_AT_DIR compile‐time option enabled] modifies
the pattern matching routine so that both ‘?’ (single‐char wild‐
card) and ‘*’ (multi‐char wildcard) do not match the directory
separator character ‘/’. (The two‐character sequence ‘‘**’’ acts
as a multi‐char wildcard that includes the directory separator in
its matched characters.) Examples:
"*.c" matches "foo.c" but not "mydir/foo.c"
"**.c" matches both "foo.c" and "mydir/foo.c"
"*/*.c" matches "bar/foo.c" but not "baz/bar/foo.c"
"??*/*" matches "ab/foo" and "abc/foo"
but not "a/foo" or "a/b/foo"
This modified behaviour is equivalent to the pattern matching
style used by the shells of some of UnZip’s supported target OSs
(one example is Acorn RISC OS). This option may not be available
on systems where the Zip archive’s internal directory separator
character ‘/’ is allowed as regular character in native operating
system filenames. (Currently, UnZip uses the same pattern match‐
ing rules for both wildcard zipfile specifications and zip entry
selection patterns in most ports. For systems allowing ‘/’ as
regular filename character, the ‐W option would not work as ex‐
pected on a wildcard zipfile specification.)
-X [VMS, Unix, OS/2, NT, Tandem] restore owner/protection info (UICs