Zip (file Format) Article Index for
Zip
Website Links For
Zip
 

Information About

Zip (file Format)





File Information

  Name ZIP
  Caption A zip archive icon from the Nuvola icon set
  Extension <tt>zip</tt>
  Mime <code>application/zip</code>
  Uniform Type compkwarezip-archive
  Magic <code>PK or PK (empty archive)</code> (unless a bootstrap script is present)
  Owner Phil Katz
  Genre Data Compression


The ZIP File Format is a popular Data Compression and Archival Format . A ZIP file contains one or more files that have been compressed, to reduce their file size, or stored as-is.

The format was originally designed by Phil Katz for PKZIP . However, many software utilities other than PKZIP itself are now available to create, modify, or open (unzip, decompress) ZIP files, notably WinZip , BOMArchiveHelper , KGB Archiver , PicoZip , Info-ZIP , WinRAR , IZArc , 7-Zip , ALZip , TUGZip , Universal Extractor and Zip Genius. Microsoft has included built-in ZIP support (under the name "compressed folders") in later versions of its Windows Operating System . Apple has included built-in ZIP support in Mac OS X 10.3 and later via the BOMArchiveHelper utility.

ZIP files generally use the File Extension s ".zip" or ".ZIP" and the MIME media type application/zip. Some software uses the ZIP file format as a wrapper for a large number of small items in a specific structure. Generally when this is done a different file extension is used. Examples of this usage are Java JAR files, Id Software .pk3/.pk4 files, package files for StepMania and Winamp / Windows Media Player skins, XPInstall , as well as OpenDocument and Office Open XML office formats. Both OpenDocument and Office Open XML formats use the JAR file format internally, so files can be easily uncompressed and compressed using tools for ZIP files. Google Earth makes use of KMZ files, which are just KML files in ZIP format. Mozilla Firefox Add-ons are zip files with extension "xpi". Nokia's Mobile Phone Themes Are zipped with extension of "nth".


HISTORY


Early history

The ZIP file format was originally created by Phil Katz , founder of PKWARE , after a prolonged legal dispute between PKWARE and System Enhancement Associates (SEA) over the trademark "ARC" (short for "Archive") and the file extension .ARC .

PKWARE's first archive product, PKARC, borrowed heavily from SEA's published code, and improved on it by converting SEA's ARC C code into hand-optimised assembler, which was much faster. PKARC also used the ".ARC" file extension. SEA contended that Katz had based his product on their code and trademark, and thus ought to license the code from them and pay royalties. PKWARE refused. SEA brought a successful copyright infringement lawsuit against Phil Katz and PKWARE. After suit was brought, Katz briefly released a relabeled version of PKARC named PKPAK in a futile effort to invalidate the suit.

During settlement, Katz still refused to pay license fees to SEA, instead agreeing to pay SEA's legal expenses and stop selling PKARC. He then went on to create his own file format, which is known worldwide now as the ZIP format (commonly called a "ZIP file"). The ZIP format was more resistant to data loss than the ARC format because of redundant catalog storage; it also was more flexible than ARC, providing room for additional optional compression algorithms and future expansion. Along with the new format, PKZIP included at least one compression algorithm more efficient than any supported by ARC. Once PKZIP was released, many users abandoned ARC because of its slower speed and less effective compression, and because Katz had successfully put forth the idea that he was the "good guy" who was being treated unfairly by an "evil corporation".

Katz publicly released technical documentation on the ZIP file format making it an Open Format , along with the first version of his PKZIP archiver, in January 1989 .

The name ''zip'' (meaning ''speed'') was suggested by Katz's friend Robert Mahoney. They wanted to imply that their product would be faster than ARC and other compression formats of the time.


Moving beyond the command line

.]]
In the mid 1990s, as more new computers included Graphical User Interface s, more users were not comfortable with the Command-line operation of PKZIP. Seeing an opportunity, Shareware authors began pitching compression and archival programs with graphical user interfaces. Many of these used the ZIP format. WinZip was among the most popular. PKWARE also offered a graphical version of PKZIP. These programs were easier to learn than the older command-line equivalents, but users still had to learn a specialized tool with its own interface for file archival and compression.

In the late 1990s, various File Manager software started integrating support for the ZIP format into their user interface. Even earlier, Norton Commander and its Clones like Volkov Commander in DOS had started that trend, and that remains the norm for the "Commander-like" or Orthodox File Manager s like Midnight Commander for Linux and UNIX-like systems and Total Commander (previously Windows Commander) for Windows. The KDE file manager (kfm) supported the ZIP format very early; ZIP support was also first added to Windows Explorer with the Plus! enhancement package in Windows 98 and later included in Windows Me and Windows XP ; ZIP format support is also built in the Mac OS Finder (as of Mac OS X , via the BOMArchiveHelper utility), the Nautilus file manager used by GNOME and the Konqueror file manager of newer versions of KDE. By 2002 , all major Desktop Environment s included ZIP file support in their file managers: a ZIP file is typically presented as a directory or folder, so that files are copied into and out of it in the same manner as any other folder and the compression is handled in a way largely transparent to the user. This has eliminated the need to learn a specialized tool and interface for file archival and compression.


TECHNICAL INFORMATION

ZIP is a fairly simple archive format that compresses every file separately. Compressing files separately allows for individual files to be retrieved without reading through other data; in theory, it may allow better compression by using different algorithms for different files. However a caveat to this is that archives containing a large number of small files end up significantly larger than if they were compressed as a single file (the classic example of the latter is the common Tar.gz archive which consists of a TAR archive compressed using Gzip ).

The specification for ZIP indicates that files can be stored either uncompressed or using a variety of compression algorithms. However, in practice, ZIP is almost always used with Katz's DEFLATE Algorithm , except when files being added are already compressed or are resistant to compression.

ZIP supports a simple s, but it could also be used with other removable media).

New features including new ) Encryption, Filename Encryption, File Authentication. Application Note on the .ZIP file format

The original ZIP format had a number of limits (uncompressed size of a file, compressed size of a file and total size of the archive) at 4GB. In version 4.5 of the specification, PKWARE introduced the "ZIP64" format extensions to get around these limitations.

The FAT Filesystem of DOS only has a timestamp resolution of two seconds; ZIP file records mimic this. As a result, the built-in timestamp resolution of files in a ZIP archive is only two seconds, though extra fields can be used to store more accurate timestamps.

Since September 2006, the ZIP specification (APPNOTE.TXT) contains a provision to store file names using UTF-8 , finally adding Unicode compatibility to ZIP.

The Info-ZIP implementations of the ZIP format adds support for Unix filesystem features, such as user and group IDs, file permissions, and support for symbolic links. The Apache Ant implementation is aware of them to the extent that it can create files with predefined Unix permissions.

The Info-ZIP Windows tools also support NTFS filesystem permissions, and will make an attempt to translate from NTFS permissions to Unix permissions or vice-versa when extracting files. This can result in potentially unintended combinations, e.g. .exe files being created on NTFS volumes with executable permission denied.


REFERENCES



SEE ALSO



EXTERNAL LINKS