Merging upstream version 1.12.
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
parent
d2621fb521
commit
3708015695
19 changed files with 83 additions and 95 deletions
|
@ -6,8 +6,8 @@
|
|||
@finalout
|
||||
@c %**end of header
|
||||
|
||||
@set UPDATED 19 November 2024
|
||||
@set VERSION 1.12-rc1
|
||||
@set UPDATED 9 January 2025
|
||||
@set VERSION 1.12
|
||||
|
||||
@dircategory Compression
|
||||
@direntry
|
||||
|
@ -51,7 +51,7 @@ This manual is for Plzip (version @value{VERSION}, @value{UPDATED}).
|
|||
@end menu
|
||||
|
||||
@sp 1
|
||||
Copyright @copyright{} 2009-2024 Antonio Diaz Diaz.
|
||||
Copyright @copyright{} 2009-2025 Antonio Diaz Diaz.
|
||||
|
||||
This manual is free documentation: you have unlimited permission to copy,
|
||||
distribute, and modify it.
|
||||
|
@ -84,7 +84,7 @@ faster than lzip, at the cost of a slightly reduced compression ratio (0.4
|
|||
to 2 percent larger compressed files). Note that the number of usable
|
||||
threads is limited by file size; on files larger than a few GB plzip can use
|
||||
hundreds of processors, but on files smaller than @w{1 MiB} plzip is no faster
|
||||
than lzip (even at compression level -0). @xref{Minimum file sizes}.
|
||||
than lzip (not even at compression level -0). @xref{Minimum file sizes}.
|
||||
|
||||
For creation and manipulation of compressed tar archives
|
||||
@uref{http://www.nongnu.org/lzip/manual/tarlz_manual.html,,tarlz} can be more
|
||||
|
@ -99,8 +99,7 @@ taking into account both data integrity and decoder availability:
|
|||
|
||||
@itemize @bullet
|
||||
@item
|
||||
The lzip format provides very safe integrity checking and some data
|
||||
recovery means. The program
|
||||
The program
|
||||
@uref{http://www.nongnu.org/lzip/manual/lziprecover_manual.html#Data-safety,,lziprecover}
|
||||
can repair bit flip errors (one of the most common forms of data corruption)
|
||||
in lzip files, and provides data recovery capabilities, including
|
||||
|
@ -509,8 +508,7 @@ POSIX recommends these conventions for command-line arguments.
|
|||
@item Certain options require an argument.
|
||||
|
||||
@item An option and its argument may or may not appear as separate tokens.
|
||||
(In other words, the whitespace separating them is optional, unless the
|
||||
argument is the empty string).
|
||||
(In other words, the whitespace separating them is optional).
|
||||
Thus, @w{@option{-o foo}} and @option{-ofoo} are equivalent.
|
||||
|
||||
@item One or more options without arguments, followed by at most one option
|
||||
|
@ -541,11 +539,6 @@ tokens. In the latter case they must be separated by an equal sign @samp{=}.
|
|||
Thus, @w{@option{--foo bar}} and @option{--foo=bar} are equivalent.
|
||||
@end itemize
|
||||
|
||||
@noindent
|
||||
The syntax of options with an optional argument is
|
||||
@option{-<short_option><argument>} (without whitespace), or
|
||||
@option{--<long_option>=<argument>}.
|
||||
|
||||
|
||||
@node File format
|
||||
@chapter File format
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue