Debian Codegraph @

README

raw
1 Zip 3.0 is the first Zip update adding large file support. For now Zip 2.3x
2 remains available and supported, but users should switch to this new release.
3
4 Testing for Zip 3.0 has focused mainly on Unix, VMS, Max OS X, and Win32,
5 and some other ports may not be fully supported yet. If you find your
6 favorite port is broke, send us the details or, better, send bug fixes. It's
7 possible that support for some older ports may be dropped in the future.
8
9
10
11 Copyright (c) 1990-2008 Info-ZIP. All rights reserved.
12
13 See the accompanying file LICENSE (the contents of which are also included
14 in unzip.h, zip.h and wiz.h) for terms of use. If, for some reason, all
15 of these files are missing, the Info-ZIP license also may be found at:
16 ftp://ftp.info-zip.org/pub/infozip/license.html and
17 http://www.info-zip.org/pub/infozip/license.html.
18
19
20 Zip 3.0 is a compression and file packaging utility. It is compatible with
21 PKZIP 2.04g (Phil Katz ZIP) for MSDOS systems. There is a companion to zip
22 called unzip (of course) which you should be able to find in the same place
23 you got zip. See the file 'WHERE' for details on ftp sites and mail
24 servers.
25
26 So far zip has been ported to a wide array of Unix and other mainframes,
27 minis, and micros including VMS, OS/2, Minix, MSDOS, Windows, Atari, Amiga,
28 BeOS and VM/CMS. Although highly compatible with PKware's PKZIP and PKUNZIP
29 utilities of MSDOS fame, our primary objective has been one of portability
30 and other-than-MSDOS functionality. Features not found in the PKWare version
31 include creation of zip files in a pipe or on a device; VMS, BeOS and OS/2
32 extended file attributes; conversion from Unix to MSDOS text file format; and,
33 of course, the ability to run on most of your favorite operating systems. And
34 it's free.
35
36 See the file zip30.ann for a summary of new features in Zip 3.0 and WhatsNew
37 for the detailed list of new features and changes since Zip 2.32. The file
38 CHANGES details all day-to-day changes during development.
39
40 Notes:
41
42 Multi-volume support. This version does not support multi-volume spanned
43 archives as in pkzip 2.04g, and there is no intention at this point to support
44 spanned archives, but Zip 3.0 supports split archives. A split archive is an
45 archive split into a set of files, each file a piece of the archive and each
46 file using an extension, such as .z02 as in the file name archive.z02, that
47 provides the order of the splits. In contrast, a spanned archive is the
48 original multi-floppy archive supported by pkzip 2.0g where the split order
49 is contained in the volume labels. The contents of split and spanned archives
50 are mostly identical and there is a simple procedure to convert between the
51 formats. Many current unzips now support split archives.
52
53 Zip64 support. This version supports Zip64 archives as described in the
54 PKWare AppNote. These archives use additional fields to support archives
55 greater than 2 GB and files in archives over the 2 GB previous limit (4 GB
56 on some ports). The Zip64 format also allows more than 64k entries in an
57 archive. Support by the OS for files larger than 4 GB is needed for Zip to
58 create and read large files and archives. On Unix, Win32, and some other
59 ports, large file and Zip64 support is automatically checked for and
60 compiled in if available. Use of Zip64 by Zip is automatic and to maximize
61 backward compatibility the Zip64 fields will only be used if needed. A
62 Zip64 archive requires a pkzip 4.5 compatible unzip, such as UnZip 6.0.
63
64 Unicode support. This version has initial Unicode support. This allows
65 paths and names of files in other character sets to be accurately recreated
66 on OS that have sufficient character set support. On Win32, if wide
67 character calls are supported (not Win 9x unless Unicode support has been
68 added) all files (including paths with illegal characters in the current
69 character set) should now be readable by zip. Unicode support is provided
70 using a new set of UTF-8 path and comment extra fields and a new UTF-8 bit
71 for flagging when the current character set is already UTF-8. Zip 3.0
72 maintains backward compatibility with older archives and is mostly compliant
73 with the new Unicode additions in the latest PKWare AppNote. The exception
74 is UTF-8 comments, which are not supported if UTF-8 is not the native
75 character set, but should be fully implemented in Zip 3.1.
76
77 16-bit OS support. Though Zip 3.0 is designed to support the latest zip
78 standards and modern OS, some effort has been made to maintain support
79 for older and smaller systems. If you find Zip 3.0 does not fit on or
80 otherwise does not work well on a particular OS, send in the details and
81 we might be able to help.
82
83 Compression methods. In addition to the standard store and deflate methods,
84 Zip now can use the bzip2 compression format using the bzip2 library. Though
85 bzip2 compression generally takes longer, in many cases using bzip2 results
86 in much better compression. However, many unzips may not yet support
87 bzip2 compressed entries in archives, so test your unzip first before using
88 bzip2 compression.
89
90 Installation. Please read the file INSTALL for information on how to compile
91 and install zip, zipsplit, zipcloak, and zipnote and please read the manual
92 pages ZIP.txt, ZIPSPLIT.txt, ZIPCLOAK.txt, and ZIPNOTE.txt for information on
93 how to use them. Also, if you are using MSDOS or Windows, note that text
94 files in the distribution are generally in Unix line end format (LF only)
95 and Windows and DOS users will need to either convert the files as needed to
96 DOS line ends (CR LF) or extract the distribution contents using unzip -a.
97
98 Utilities. At this point zipsplit, zipcloak, and zipnote should work with
99 large files, but they currently do not handle split archives. A work around
100 is to use zip to convert a split archive to a single file archive and then use
101 the utilities on that archive.
102
103 Encryption. This version supports standard zip encryption. Until recently
104 the encryption code was distributed separately because of the US export
105 regulations but now is part of the main distribution. See crypt.c for
106 details. Decryption can be made with unzip 5.0p1 or later, or with zipcloak.
107
108 Bug reports. All bug reports or patches should go to zip-bugs via the web
109 site contact form at http://www.info-zip.org/zip-bug.html (we have discontinued
110 the old email address [email protected] because of too much spam lately)
111 and suggestions for new features can be submitted there also (although we don't
112 promise to use all of them). We also are on SourceForge at
113 http://sourceforge.net/projects/infozip/ and now automatically get Bug Reports
114 and Feature Requests submitted there. In addition, a new Info-ZIP discussion
115 forum is available as well. See below. Though bug reports can be posted there,
116 we don't have automatic monitoring of all postings set up yet so you may want
117 to use the web form or SoureForge for a quicker response. A good approach may
118 be to post the details on the forum so others can benefit from the posting,
119 then use the web reply form to let us know you did that if you don't get a
120 reply in a reasonable time.
121
122 Ports. If you're considering a port, please check in with zip-bugs FIRST,
123 since the code is constantly being updated behind the scenes. We'll
124 arrange to give you access to the latest source.
125
126 Discussion group. If you'd like to keep up to date with our Zip (and companion
127 UnZip utility) development, join the ranks of BETA testers, add your own
128 thoughts and contributions, etc., check out the new discussion forum. This is
129 the latest offering, after the various Info-ZIP mailing-lists on
130 [email protected] (courtesy of Hunter Goatley) were no longer available
131 and the temporary QuickTopic discussion group for Info-ZIP issues at
132 http://www.quicktopic.com/27/H/V6ZQZ54uKNL died a horrible death due to large
133 amounts of spam. The new discussion forum is now available at
134 http://www.info-zip.org/board/board.pl (thanks again to Hunter Goatley) and
135 can be used to discuss issues, request features, and is one place new betas
136 and releases are announced. It also is a place to post bug reports, and
137 patches can be submitted as attachments. However, we don't yet get
138 automatic notification of all postings there so try one of the other methods
139 if you don't get a response. You can also post Bug Reports and Feature
140 Requests at Source Forge. However, the web site contact form remains
141 available if you would rather not post on the public forums.
142
143 Frequently asked questions on zip and unzip:
144
145 Q. When unzipping I get an error message about "compression method 8".
146
147 A. This is standard deflate, which has been around for awhile. Please
148 get a current version of unzip. See the file 'WHERE' for details.
149
150
151 Q. How about "compression method 12"?
152
153 A. Compression method 12 is bzip2 and requires a relatively modern unzip.
154 Please get the latest version of unzip.
155
156
157 Q. I can't extract this zip file that I just downloaded. I get
158 "zipfile is part of multi-disk archive" or some other message.
159
160 A. Please make sure that you made the transfer in binary mode. Check
161 in particular that your copy has exactly the same size as the original.
162 Note that the above message also may actually mean you have only part
163 of a multi-part archive. Also note that UnZip 5.x does not and UnZip 6.0
164 probably won't have multi-disk (split) archive support. A work around
165 is to use Zip 3.0 to convert the split archive to a single-file archive
166 then use UnZip on that archive. As a last result, if there's something
167 readable in what you have, zip -FF should be able to recover it.
168
169
170 Q. When running unzip, I get a message about "End-of-central-directory
171 signature not found".
172
173 A. This usually means that your zip archive is damaged, or that you
174 have an uncompressed file with the same name in the same directory.
175 In the first case, it makes more sense to contact the person you
176 obtained the zip file from rather than the Info-ZIP software
177 developers, and to make sure that your copy is strictly identical to
178 the original. In the second case, use "unzip zipfile.zip" instead
179 of "unzip zipfile", to let unzip know which file is the zip archive
180 you want to extract.
181
182
183 Q. Why doesn't zip do <something> just like PKZIP does?
184
185 A. Zip is not a PKZIP clone and is not intended to be one. In some
186 cases we feel PKZIP does not do the right thing (e.g., not
187 including pathnames by default); in some cases the operating system
188 itself is responsible (e.g., under Unix it is the shell which
189 expands wildcards, not zip). Info-ZIP's and PKWARE's zipfiles
190 are interchangeable, not the programs.
191
192 For example, if you are used to the following PKZIP command:
193 pkzip -rP foo *.c
194 you must use instead on Unix:
195 zip -R foo "*.c"
196 (the quotes are needed to let the shell know that it should
197 not expand the *.c argument but instead pass it on to the program,
198 but are not needed on ports that do not expand file paths like
199 MSDOS)
200
201
202 Q. Can I distribute zip and unzip sources and/or executables?
203
204 A. You may redistribute the latest official distributions without any
205 modification, without even asking us for permission. You can charge
206 for the cost of the media (CDROM, diskettes, etc...) and a small copying
207 fee. If you want to distribute modified versions please contact us at
208 www.Info-ZIP.org first. You must not distribute beta versions.
209 The latest official distributions are always on ftp.Info-ZIP.org in
210 directory /pub/infozip and subdirectories and at SourceForge.
211
212
213 Q. Can I use the executables of zip and unzip to distribute my software?
214
215 A. Yes, so long as it is made clear in the product documentation that
216 zip or unzip are not being sold, that the source code is freely
217 available, and that there are no extra or hidden charges resulting
218 from its use by or inclusion with the commercial product. See the
219 Info-ZIP license for more. Here is an example of a suitable notice:
220
221 NOTE: <Product> is packaged on this CD using Info-ZIP's compression
222 utility. The installation program uses UnZip to read zip files from
223 the CD. Info-ZIP's software (Zip, UnZip and related utilities) is
224 freely distributed under the Info-ZIP license and can be obtained as
225 source code or executables from various anonymous-ftp sites,
226 including ftp://ftp.info-zip.org/pub/infozip.
227
228
229 Q. Can I use the source code of zip and unzip in my commercial application?
230
231 A. Yes, as long as the conditions in the Info-ZIP license are met. We
232 recommend you include in your product documentation an acknowledgment
233 and note that the original compression sources are available at
234 www.Info-ZIP.org. If you have special requirements contact us.