Adding upstream version 1.0~rc3.
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
parent
c6f07d4c80
commit
a3b3475883
13 changed files with 267 additions and 266 deletions
|
@ -1,5 +1,5 @@
|
|||
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.36.
|
||||
.TH CLZIP "1" "February 2010" "Clzip 1.0-rc2" "User Commands"
|
||||
.TH CLZIP "1" "March 2010" "Clzip 1.0-rc3" "User Commands"
|
||||
.SH NAME
|
||||
Clzip \- data compressor based on the LZMA algorithm
|
||||
.SH SYNOPSIS
|
||||
|
|
|
@ -12,7 +12,7 @@ File: clzip.info, Node: Top, Next: Introduction, Up: (dir)
|
|||
Clzip Manual
|
||||
************
|
||||
|
||||
This manual is for Clzip (version 1.0-rc2, 21 February 2010).
|
||||
This manual is for Clzip (version 1.0-rc3, 13 March 2010).
|
||||
|
||||
* Menu:
|
||||
|
||||
|
@ -68,11 +68,11 @@ multivolume compressed tar archives.
|
|||
The amount of memory required for compression is about 5 MiB plus 1
|
||||
or 2 times the dictionary size limit (1 if input file size is less than
|
||||
dictionary size limit, else 2) plus 8 times the dictionary size really
|
||||
used. For decompression is a little more than the dictionary size really
|
||||
used. Clzip will automatically use the smallest possible dictionary size
|
||||
without exceeding the given limit. It is important to appreciate that
|
||||
the decompression memory requirement is affected at compression time by
|
||||
the choice of dictionary size limit.
|
||||
used. For decompression it is a little more than the dictionary size
|
||||
really used. Clzip will automatically use the smallest possible
|
||||
dictionary size without exceeding the given limit. It is important to
|
||||
appreciate that the decompression memory requirement is affected at
|
||||
compression time by the choice of dictionary size limit.
|
||||
|
||||
When decompressing, clzip attempts to guess the name for the
|
||||
decompressed file from that of the compressed file as follows:
|
||||
|
@ -432,7 +432,7 @@ Concept Index
|
|||
|
||||
Tag Table:
|
||||
Node: Top226
|
||||
Node: Introduction838
|
||||
Node: Introduction835
|
||||
Node: Algorithm4160
|
||||
Node: Invoking Clzip6391
|
||||
Node: File Format10747
|
||||
|
|
|
@ -5,8 +5,8 @@
|
|||
@finalout
|
||||
@c %**end of header
|
||||
|
||||
@set UPDATED 21 February 2010
|
||||
@set VERSION 1.0-rc2
|
||||
@set UPDATED 13 March 2010
|
||||
@set VERSION 1.0-rc3
|
||||
|
||||
@dircategory Data Compression
|
||||
@direntry
|
||||
|
@ -84,11 +84,11 @@ compressed tar archives.
|
|||
The amount of memory required for compression is about 5 MiB plus 1 or 2
|
||||
times the dictionary size limit (1 if input file size is less than
|
||||
dictionary size limit, else 2) plus 8 times the dictionary size really
|
||||
used. For decompression is a little more than the dictionary size really
|
||||
used. Clzip will automatically use the smallest possible dictionary size
|
||||
without exceeding the given limit. It is important to appreciate that
|
||||
the decompression memory requirement is affected at compression time by
|
||||
the choice of dictionary size limit.
|
||||
used. For decompression it is a little more than the dictionary size
|
||||
really used. Clzip will automatically use the smallest possible
|
||||
dictionary size without exceeding the given limit. It is important to
|
||||
appreciate that the decompression memory requirement is affected at
|
||||
compression time by the choice of dictionary size limit.
|
||||
|
||||
When decompressing, clzip attempts to guess the name for the decompressed
|
||||
file from that of the compressed file as follows:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue