1ZIPINFO(1L) ZIPINFO(1L)
2
6 zipinfo - list detailed information about a ZIP archive
7
9 zipinfo [-12smlvhMtTz] file[.zip] [file(s) ...] [-x xfile(s) ...]
10 unzip -Z [-12smlvhMtTz] file[.zip] [file(s) ...] [-x xfile(s) ...]
12
14 zipinfo lists technical information about files in a ZIP archive, most
15 commonly found on MS-DOS systems. Such information includes file
16 access permissions, encryption status, type of compression, version and
17 operating system or file system of compressing program, and the like.
18 The default behavior (with no options) is to list single-line entries
19 for each file in the archive, with header and trailer lines providing
20 summary information for the entire archive. The format is a cross
21 between Unix ``ls -l'' and ``unzip -v'' output. See DETAILED DESCRIP‐
22 TION below. Note that zipinfo is the same program as unzip (under
23 Unix, a link to it); on some systems, however, zipinfo support may have
24 been omitted when unzip was compiled.
25
27 file[.zip]
28 Path of the ZIP archive(s). If the file specification is a
29 wildcard, each matching file is processed in an order determined
30 by the operating system (or file system). Only the filename can
31 be a wildcard; the path itself cannot. Wildcard expressions are
32 similar to Unix egrep(1) (regular) expressions and may contain:
33 * matches a sequence of 0 or more characters
35 ? matches exactly 1 character
37 [...] matches any single character found inside the brackets;
39 ranges are specified by a beginning character, a hyphen,
40 and an ending character. If an exclamation point or a
41 caret (`!' or `^') follows the left bracket, then the
42 range of characters within the brackets is complemented
43 (that is, anything except the characters inside the
44 brackets is considered a match). To specify a verbatim
45 left bracket, the three-character sequence ``[[]'' has to
46 be used.
47 (Be sure to quote any character that might otherwise be inter‐
49 preted or modified by the operating system, particularly under
50 Unix and VMS.) If no matches are found, the specification is
51 assumed to be a literal filename; and if that also fails, the
52 suffix .zip is appended. Note that self-extracting ZIP files
53 are supported, as with any other ZIP archive; just specify the
54 .exe suffix (if any) explicitly.
55 [file(s)]
57 An optional list of archive members to be processed, separated
58 by spaces. (VMS versions compiled with VMSCLI defined must
59 delimit files with commas instead.) Regular expressions (wild‐
60 cards) may be used to match multiple members; see above. Again,
61 be sure to quote expressions that would otherwise be expanded or
62 modified by the operating system.
63 [-x xfile(s)]
65 An optional list of archive members to be excluded from process‐
66 ing.
67
69 -1 list filenames only, one per line. This option excludes all
70 others; headers, trailers and zipfile comments are never
71 printed. It is intended for use in Unix shell scripts.
72 -2 list filenames only, one per line, but allow headers (-h),
74 trailers (-t) and zipfile comments (-z), as well. This option
75 may be useful in cases where the stored filenames are particu‐
76 larly long.
77 -s list zipfile info in short Unix ``ls -l'' format. This is the
79 default behavior; see below.
80 -m list zipfile info in medium Unix ``ls -l'' format. Identical to
82 the -s output, except that the compression factor, expressed as
83 a percentage, is also listed.
84 -l list zipfile info in long Unix ``ls -l'' format. As with -m
86 except that the compressed size (in bytes) is printed instead of
87 the compression ratio.
88 -v list zipfile information in verbose, multi-page format.
90 -h list header line. The archive name, actual size (in bytes) and
92 total number of files is printed.
93 -M pipe all output through an internal pager similar to the Unix
95 more(1) command. At the end of a screenful of output, zipinfo
96 pauses with a ``--More--'' prompt; the next screenful may be
97 viewed by pressing the Enter (Return) key or the space bar.
98 zipinfo can be terminated by pressing the ``q'' key and, on some
99 systems, the Enter/Return key. Unlike Unix more(1), there is no
100 forward-searching or editing capability. Also, zipinfo doesn't
101 notice if long lines wrap at the edge of the screen, effectively
102 resulting in the printing of two or more lines and the likeli‐
103 hood that some text will scroll off the top of the screen before
104 being viewed. On some systems the number of available lines on
105 the screen is not detected, in which case zipinfo assumes the
106 height is 24 lines.
107 -t list totals for files listed or for all files. The number of
109 files listed, their uncompressed and compressed total sizes ,
110 and their overall compression factor is printed; or, if only the
111 totals line is being printed, the values for the entire archive
112 are given. The compressed total size does not include the 12
113 additional header bytes of each encrypted entry. Note that the
114 total compressed (data) size will never match the actual zipfile
115 size, since the latter includes all of the internal zipfile
116 headers in addition to the compressed data.
117 -T print the file dates and times in a sortable decimal format
119 (yymmdd.hhmmss). The default date format is a more standard,
120 human-readable version with abbreviated month names (see exam‐
121 ples below).
122 -U [UNICODE_SUPPORT only] modify or disable UTF-8 handling. When
124 UNICODE_SUPPORT is available, the option -U forces unzip to
125 escape all non-ASCII characters from UTF-8 coded filenames as
126 ``#Uxxxx''. This option is mainly provided for debugging pur‐
127 pose when the fairly new UTF-8 support is suspected to mangle up
128 extracted filenames.
129 The option -UU allows to entirely disable the recognition of
131 UTF-8 encoded filenames. The handling of filename codings
132 within unzip falls back to the behaviour of previous versions.
133 -z include the archive comment (if any) in the listing.
135
137 zipinfo has a number of modes, and its behavior can be rather difficult
138 to fathom if one isn't familiar with Unix ls(1) (or even if one is).
139 The default behavior is to list files in the following format:
140 -rw-rws--- 1.9 unx 2802 t- defX 11-Aug-91 13:48 perms.2660
142 The last three fields are the modification date and time of the file,
144 and its name. The case of the filename is respected; thus files that
145 come from MS-DOS PKZIP are always capitalized. If the file was zipped
146 with a stored directory name, that is also displayed as part of the
147 filename.
148 The second and third fields indicate that the file was zipped under
150 Unix with version 1.9 of zip. Since it comes from Unix, the file per‐
151 missions at the beginning of the line are printed in Unix format. The
152 uncompressed file-size (2802 in this example) is the fourth field.
153 The fifth field consists of two characters, either of which may take on
155 several values. The first character may be either `t' or `b', indicat‐
156 ing that zip believes the file to be text or binary, respectively; but
157 if the file is encrypted, zipinfo notes this fact by capitalizing the
158 character (`T' or `B'). The second character may also take on four
159 values, depending on whether there is an extended local header and/or
160 an ``extra field'' associated with the file (fully explained in
161 PKWare's APPNOTE.TXT, but basically analogous to pragmas in ANSI
162 C--i.e., they provide a standard way to include non-standard informa‐
163 tion in the archive). If neither exists, the character will be a
164 hyphen (`-'); if there is an extended local header but no extra field,
165 `l'; if the reverse, `x'; and if both exist, `X'. Thus the file in
166 this example is (probably) a text file, is not encrypted, and has nei‐
167 ther an extra field nor an extended local header associated with it.
168 The example below, on the other hand, is an encrypted binary file with
169 an extra field:
170 RWD,R,R 0.9 vms 168 Bx shrk 9-Aug-91 19:15 perms.0644
172 Extra fields are used for various purposes (see discussion of the -v
174 option below) including the storage of VMS file attributes, which is
175 presumably the case here. Note that the file attributes are listed in
176 VMS format. Some other possibilities for the host operating system
177 (which is actually a misnomer--host file system is more correct)
178 include OS/2 or NT with High Performance File System (HPFS), MS-DOS,
179 OS/2 or NT with File Allocation Table (FAT) file system, and Macintosh.
180 These are denoted as follows:
181 -rw-a-- 1.0 hpf 5358 Tl i4:3 4-Dec-91 11:33 longfilename.hpfs
183 -r--ahs 1.1 fat 4096 b- i4:2 14-Jul-91 12:58 EA DATA. SF
184 --w------- 1.0 mac 17357 bx i8:2 4-May-92 04:02 unzip.macr
185 File attributes in the first two cases are indicated in a Unix-like
187 format, where the seven subfields indicate whether the file: (1) is a
188 directory, (2) is readable (always true), (3) is writable, (4) is exe‐
189 cutable (guessed on the basis of the extension--.exe, .com, .bat, .cmd
190 and .btm files are assumed to be so), (5) has its archive bit set, (6)
191 is hidden, and (7) is a system file. Interpretation of Macintosh file
192 attributes is unreliable because some Macintosh archivers don't store
193 any attributes in the archive.
194 Finally, the sixth field indicates the compression method and possible
196 sub-method used. There are six methods known at present: storing (no
197 compression), reducing, shrinking, imploding, tokenizing (never pub‐
198 licly released), and deflating. In addition, there are four levels of
199 reducing (1 through 4); four types of imploding (4K or 8K sliding dic‐
200 tionary, and 2 or 3 Shannon-Fano trees); and four levels of deflating
201 (superfast, fast, normal, maximum compression). zipinfo represents
202 these methods and their sub-methods as follows: stor; re:1, re:2,
203 etc.; shrk; i4:2, i8:3, etc.; tokn; and defS, defF, defN, and defX.
204 The medium and long listings are almost identical to the short format
206 except that they add information on the file's compression. The medium
207 format lists the file's compression factor as a percentage indicating
208 the amount of space that has been ``removed'':
209 -rw-rws--- 1.5 unx 2802 t- 81% defX 11-Aug-91 13:48 perms.2660
211 In this example, the file has been compressed by more than a factor of
213 five; the compressed data are only 19% of the original size. The long
214 format gives the compressed file's size in bytes, instead:
215 -rw-rws--- 1.5 unx 2802 t- 538 defX 11-Aug-91 13:48 perms.2660
217 In contrast to the unzip listings, the compressed size figures in this
219 listing format denote the complete size of compressed data, including
220 the 12 extra header bytes in case of encrypted entries.
221 Adding the -T option changes the file date and time to decimal format:
223 -rw-rws--- 1.5 unx 2802 t- 538 defX 910811.134804 perms.2660
225 Note that because of limitations in the MS-DOS format used to store
227 file times, the seconds field is always rounded to the nearest even
228 second. For Unix files this is expected to change in the next major
229 releases of zip(1L) and unzip.
230 In addition to individual file information, a default zipfile listing
232 also includes header and trailer lines:
233 Archive: OS2.zip 5453 bytes 5 files
235 ,,rw, 1.0 hpf 730 b- i4:3 26-Jun-92 23:40 Contents
236 ,,rw, 1.0 hpf 3710 b- i4:3 26-Jun-92 23:33 makefile.os2
237 ,,rw, 1.0 hpf 8753 b- i8:3 26-Jun-92 15:29 os2unzip.c
238 ,,rw, 1.0 hpf 98 b- stor 21-Aug-91 15:34 unzip.def
239 ,,rw, 1.0 hpf 95 b- stor 21-Aug-91 17:51 zipinfo.def
240 5 files, 13386 bytes uncompressed, 4951 bytes compressed: 63.0%
241 The header line gives the name of the archive, its total size, and the
243 total number of files; the trailer gives the number of files listed,
244 their total uncompressed size, and their total compressed size (not
245 including any of zip's internal overhead). If, however, one or more
246 file(s) are provided, the header and trailer lines are not listed.
247 This behavior is also similar to that of Unix's ``ls -l''; it may be
248 overridden by specifying the -h and -t options explicitly. In such a
249 case the listing format must also be specified explicitly, since -h or
250 -t (or both) in the absence of other options implies that ONLY the
251 header or trailer line (or both) is listed. See the EXAMPLES section
252 below for a semi-intelligible translation of this nonsense.
253 The verbose listing is mostly self-explanatory. It also lists file
255 comments and the zipfile comment, if any, and the type and number of
256 bytes in any stored extra fields. Currently known types of extra
257 fields include PKWARE's authentication (``AV'') info; OS/2 extended
258 attributes; VMS filesystem info, both PKWARE and Info-ZIP versions;
259 Macintosh resource forks; Acorn/Archimedes SparkFS info; and so on.
260 (Note that in the case of OS/2 extended attributes--perhaps the most
261 common use of zipfile extra fields--the size of the stored EAs as
262 reported by zipinfo may not match the number given by OS/2's dir com‐
263 mand: OS/2 always reports the number of bytes required in 16-bit for‐
264 mat, whereas zipinfo always reports the 32-bit storage.)
265 Again, the compressed size figures of the individual entries include
267 the 12 extra header bytes for encrypted entries. In contrast, the ar‐
268 chive total compressed size and the average compression ratio shown in
269 the summary bottom line are calculated without the extra 12 header
270 bytes of encrypted entries.
271
273 Modifying zipinfo's default behavior via options placed in an environ‐
274 ment variable can be a bit complicated to explain, due to zipinfo's
275 attempts to handle various defaults in an intuitive, yet Unix-like,
276 manner. (Try not to laugh.) Nevertheless, there is some underlying
277 logic. In brief, there are three ``priority levels'' of options: the
278 default options; environment options, which can override or add to the
279 defaults; and explicit options given by the user, which can override or
280 add to either of the above.
281 The default listing format, as noted above, corresponds roughly to the
283 "zipinfo -hst" command (except when individual zipfile members are
284 specified). A user who prefers the long-listing format (-l) can make
285 use of the zipinfo's environment variable to change this default:
286 Unix Bourne shell:
288 ZIPINFO=-l; export ZIPINFO
289 Unix C shell:
291 setenv ZIPINFO -l
292 OS/2 or MS-DOS:
294 set ZIPINFO=-l
295 VMS (quotes for lowercase):
297 define ZIPINFO_OPTS "-l"
298 If, in addition, the user dislikes the trailer line, zipinfo's concept
300 of ``negative options'' may be used to override the default inclusion
301 of the line. This is accomplished by preceding the undesired option
302 with one or more minuses: e.g., ``-l-t'' or ``--tl'', in this example.
303 The first hyphen is the regular switch character, but the one before
304 the `t' is a minus sign. The dual use of hyphens may seem a little
305 awkward, but it's reasonably intuitive nonetheless: simply ignore the
306 first hyphen and go from there. It is also consistent with the behav‐
307 ior of the Unix command nice(1).
308 As suggested above, the default variable names are ZIPINFO_OPTS for VMS
310 (where the symbol used to install zipinfo as a foreign command would
311 otherwise be confused with the environment variable), and ZIPINFO for
312 all other operating systems. For compatibility with zip(1L), ZIPIN‐
313 FOOPT is also accepted (don't ask). If both ZIPINFO and ZIPINFOOPT are
314 defined, however, ZIPINFO takes precedence. unzip's diagnostic option
315 (-v with no zipfile name) can be used to check the values of all four
316 possible unzip and zipinfo environment variables.
317
319 To get a basic, short-format listing of the complete contents of a ZIP
320 archive storage.zip, with both header and totals lines, use only the
321 archive name as an argument to zipinfo:
322 zipinfo storage
324 To produce a basic, long-format listing (not verbose), including header
326 and totals lines, use -l:
327 zipinfo -l storage
329 To list the complete contents of the archive without header and totals
331 lines, either negate the -h and -t options or else specify the contents
332 explicitly:
333 zipinfo --h-t storage
335 zipinfo storage \*
336 (where the backslash is required only if the shell would otherwise
338 expand the `*' wildcard, as in Unix when globbing is turned on--double
339 quotes around the asterisk would have worked as well). To turn off the
340 totals line by default, use the environment variable (C shell is
341 assumed here):
342 setenv ZIPINFO --t
344 zipinfo storage
345 To get the full, short-format listing of the first example again, given
347 that the environment variable is set as in the previous example, it is
348 necessary to specify the -s option explicitly, since the -t option by
349 itself implies that ONLY the footer line is to be printed:
350 setenv ZIPINFO --t
352 zipinfo -t storage [only totals line]
353 zipinfo -st storage [full listing]
354 The -s option, like -m and -l, includes headers and footers by default,
356 unless otherwise specified. Since the environment variable specified
357 no footers and that has a higher precedence than the default behavior
358 of -s, an explicit -t option was necessary to produce the full listing.
359 Nothing was indicated about the header, however, so the -s option was
360 sufficient. Note that both the -h and -t options, when used by them‐
361 selves or with each other, override any default listing of member
362 files; only the header and/or footer are printed. This behavior is
363 useful when zipinfo is used with a wildcard zipfile specification; the
364 contents of all zipfiles are then summarized with a single command.
365 To list information on a single file within the archive, in medium for‐
367 mat, specify the filename explicitly:
368 zipinfo -m storage unshrink.c
370 The specification of any member file, as in this example, will override
372 the default header and totals lines; only the single line of informa‐
373 tion about the requested file will be printed. This is intuitively
374 what one would expect when requesting information about a single file.
375 For multiple files, it is often useful to know the total compressed and
376 uncompressed size; in such cases -t may be specified explicitly:
377 zipinfo -mt storage "*.[ch]" Mak\*
379 To get maximal information about the ZIP archive, use the verbose
381 option. It is usually wise to pipe the output into a filter such as
382 Unix more(1) if the operating system allows it:
383 zipinfo -v storage | more
385 Finally, to see the most recently modified files in the archive, use
387 the -T option in conjunction with an external sorting utility such as
388 Unix sort(1) (and sed(1) as well, in this example):
389 zipinfo -T storage | sort -nr -k 7 | sed 15q
391 The -nr option to sort(1) tells it to sort numerically in reverse order
393 rather than in textual order, and the -k 7 option tells it to sort on
394 the seventh field. This assumes the default short-listing format; if
395 -m or -l is used, the proper sort(1) option would be -k 8. Older ver‐
396 sions of sort(1) do not support the -k option, but you can use the tra‐
397 ditional + option instead, e.g., +6 instead of -k 7. The sed(1) com‐
398 mand filters out all but the first 15 lines of the listing. Future
399 releases of zipinfo may incorporate date/time and filename sorting as
400 built-in options.
401
403 The author finds it convenient to define an alias ii for zipinfo on
404 systems that allow aliases (or, on other systems, copy/rename the exe‐
405 cutable, create a link or create a command file with the name ii). The
406 ii usage parallels the common ll alias for long listings in Unix, and
407 the similarity between the outputs of the two commands was intentional.
408
410 As with unzip, zipinfo's -M (``more'') option is overly simplistic in
411 its handling of screen output; as noted above, it fails to detect the
412 wrapping of long lines and may thereby cause lines at the top of the
413 screen to be scrolled off before being read. zipinfo should detect and
414 treat each occurrence of line-wrap as one additional line printed.
415 This requires knowledge of the screen's width as well as its height.
416 In addition, zipinfo should detect the true screen geometry on all sys‐
417 tems.
418 zipinfo's listing-format behavior is unnecessarily complex and should
420 be simplified. (This is not to say that it will be.)
421
423 ls(1), funzip(1L), unzip(1L), unzipsfx(1L), zip(1L), zipcloak(1L), zip‐
424 note(1L), zipsplit(1L)
425
427 The Info-ZIP home page is currently at
428 http://www.info-zip.org/pub/infozip/
429 or
430 ftp://ftp.info-zip.org/pub/infozip/ .
431
433 Greg ``Cave Newt'' Roelofs. ZipInfo contains pattern-matching code by
434 Mark Adler and fixes/improvements by many others. Please refer to the
435 CONTRIBS file in the UnZip source distribution for a more complete
436 list.
437Info-ZIP 20 April 2009 (v3.0) ZIPINFO(1L)