diff options
Diffstat (limited to 'archivers/libarchive/files/doc/html/libarchive-formats.5.html')
| -rw-r--r-- | archivers/libarchive/files/doc/html/libarchive-formats.5.html | 93 |
1 files changed, 44 insertions, 49 deletions
diff --git a/archivers/libarchive/files/doc/html/libarchive-formats.5.html b/archivers/libarchive/files/doc/html/libarchive-formats.5.html index 6172fea963c..e8a16215526 100644 --- a/archivers/libarchive/files/doc/html/libarchive-formats.5.html +++ b/archivers/libarchive/files/doc/html/libarchive-formats.5.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:10 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:18 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -34,9 +34,9 @@ library</p> <p style="margin-left:6%;">The libarchive(3) library reads and writes a variety of streaming archive formats. Generally speaking, all of these archive formats consist of a series -of ’’entries’’. Each entry stores a -single file system object, such as a file, directory, or -symbolic link.</p> +of “entries”. Each entry stores a single file +system object, such as a file, directory, or symbolic +link.</p> <p style="margin-left:6%; margin-top: 1em">The following provides a brief description of each format supported by @@ -52,10 +52,9 @@ all supported formats.</p> <p style="margin-left:6%; margin-top: 1em"><b>Tar Formats</b> <br> The libarchive(3) library can read most tar archives. It can -write POSIX-standard ’’ustar’’ and -’’pax interchange’’ formats as well -as v7 tar format and a subset of the legacy GNU tar -format.</p> +write POSIX-standard “ustar” and “pax +interchange” formats as well as v7 tar format and a +subset of the legacy GNU tar format.</p> <p style="margin-left:6%; margin-top: 1em">All tar formats store each entry in one or more 512-byte records. The first @@ -99,11 +98,10 @@ standard are in all lowercase; vendors are allowed to define custom keys by preceding them with the vendor name in all uppercase. When writing pax archives, libarchive uses many of the SCHILY keys defined by Joerg Schilling’s -’’star’’ archiver and a few -LIBARCHIVE keys. The libarchive library can read most of the -SCHILY keys and most of the GNU keys introduced by GNU tar. -It silently ignores any keywords that it does not -understand.</p> +“star” archiver and a few LIBARCHIVE keys. The +libarchive library can read most of the SCHILY keys and most +of the GNU keys introduced by GNU tar. It silently ignores +any keywords that it does not understand.</p> <p style="margin-left:17%; margin-top: 1em">The pax interchange format converts filenames to Unicode and stores @@ -241,18 +239,17 @@ extended attribute records written by Solaris tar.</p> <p style="margin-left:6%; margin-top: 1em">The first tar program appeared in Seventh Edition Unix in 1979. The first official standard for the tar file format was the -’’ustar’’ (Unix Standard Tar) format -defined by POSIX in 1988. POSIX.1-2001 extended the ustar -format to create the ’’pax -interchange’’ format.</p> +“ustar” (Unix Standard Tar) format defined by +POSIX in 1988. POSIX.1-2001 extended the ustar format to +create the “pax interchange” format.</p> <p style="margin-left:6%; margin-top: 1em"><b>Cpio Formats</b> <br> The libarchive library can read a number of common cpio -variants and can write ’’odc’’ and -’’newc’’ format archives. A cpio -archive stores each entry as a fixed-size header followed by -a variable-length filename and variable-length data. Unlike +variants and can write “odc” and +“newc” format archives. A cpio archive stores +each entry as a fixed-size header followed by a +variable-length filename and variable-length data. Unlike the tar format, the cpio format does only minimal padding of the header or file data. There are several cpio variants, which differ primarily in how they store the initial header: @@ -272,15 +269,14 @@ mtime, and 16-bit binary values for the other fields.</p> <p style="margin-left:17%; margin-top: 1em">The libarchive library can both read and write this POSIX-standard format, -which is officially known as the ’’cpio -interchange format’’ or the -’’octet-oriented cpio archive -format’’ and sometimes unofficially referred to -as the ’’old character format’’. -This format stores the header contents as octal values in -ASCII. It is standard, portable, and immune from byte-order -confusion. File sizes and mtime are limited to 33 bits (8GB -file size), other fields are limited to 18 bits.</p> +which is officially known as the “cpio interchange +format” or the “octet-oriented cpio archive +format” and sometimes unofficially referred to as the +“old character format”. This format stores the +header contents as octal values in ASCII. It is standard, +portable, and immune from byte-order confusion. File sizes +and mtime are limited to 33 bits (8GB file size), other +fields are limited to 18 bits.</p> <p style="margin-top: 1em"><b>SVR4/newc</b></p> @@ -312,10 +308,10 @@ systems with dissimilar user numbering.</p> <p style="margin-left:6%; margin-top: 1em"><b>Shar Formats</b> <br> -A ’’shell archive’’ is a shell -script that, when executed on a POSIX-compliant system, will -recreate a collection of file system objects. The libarchive -library can write two different kinds of shar archives:</p> +A “shell archive” is a shell script that, when +executed on a POSIX-compliant system, will recreate a +collection of file system objects. The libarchive library +can write two different kinds of shar archives:</p> <p style="margin-top: 1em"><b>shar</b></p> @@ -379,15 +375,15 @@ variables.</p> format</b> <br> Libarchive can read and write zip format archives that have uncompressed entries and entries compressed with the -’’deflate’’ algorithm. Other zip -compression algorithms are not supported. It can extract jar -archives, archives that use Zip64 extensions and -self-extracting zip archives. Libarchive can use either of -two different strategies for reading Zip archives: a -streaming strategy which is fast and can handle extremely -large archives, and a seeking strategy which can correctly -process self-extracting Zip archives and archives with -deleted members or other in-place modifications.</p> +“deflate” algorithm. Other zip compression +algorithms are not supported. It can extract jar archives, +archives that use Zip64 extensions and self-extracting zip +archives. Libarchive can use either of two different +strategies for reading Zip archives: a streaming strategy +which is fast and can handle extremely large archives, and a +seeking strategy which can correctly process self-extracting +Zip archives and archives with deleted members or other +in-place modifications.</p> <p style="margin-left:6%; margin-top: 1em">The streaming reader processes Zip archives as they are read. It can read @@ -468,9 +464,8 @@ Libarchive can read and write 7-Zip format archives. TODO: Need more information</p> <p style="margin-left:6%; margin-top: 1em"><b>CAB</b> <br> -Libarchive can read Microsoft Cabinet ( -’’CAB’’) format archives. TODO: Need -more information.</p> +Libarchive can read Microsoft Cabinet ( “CAB”) +format archives. TODO: Need more information.</p> <p style="margin-left:6%; margin-top: 1em"><b>LHA</b> <br> TODO: Information about libarchive’s LHA support</p> @@ -484,8 +479,8 @@ the RARv3 format. Libarchive can also read self-extracting RAR archives.</p> <p style="margin-left:6%; margin-top: 1em"><b>Warc</b> <br> -Libarchive can read and write ’’web -archives’’. TODO: Need more information</p> +Libarchive can read and write “web archives”. +TODO: Need more information</p> <p style="margin-left:6%; margin-top: 1em"><b>XAR</b> <br> Libarchive can read and write the XAR format used by many |