summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2025-01-18 06:19:30 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2025-01-18 06:19:30 +0000
commitdf83d9d834c31b31b469f71cbdd9d5b98e595697 (patch)
tree3f43285c99633e5cf66adb46f9a7061f955bf86a /README
parentReleasing debian version 1.15~rc1-1. (diff)
downloadclzip-df83d9d834c31b31b469f71cbdd9d5b98e595697.tar.xz
clzip-df83d9d834c31b31b469f71cbdd9d5b98e595697.zip
Merging upstream version 1.15.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'README')
-rw-r--r--README22
1 files changed, 10 insertions, 12 deletions
diff --git a/README b/README
index 6eb44d6..8eda4d5 100644
--- a/README
+++ b/README
@@ -28,11 +28,10 @@ alignment between tar members and lzip members.
The lzip file format is designed for data sharing and long-term archiving,
taking into account both data integrity and decoder availability:
- * The lzip format provides very safe integrity checking and some data
- recovery means. The program lziprecover can repair bit flip errors
- (one of the most common forms of data corruption) in lzip files, and
- provides data recovery capabilities, including error-checked merging
- of damaged copies of a file.
+ * The program lziprecover can repair bit flip errors (one of the most
+ common forms of data corruption) in lzip files, and provides data
+ recovery capabilities, including error-checked merging of damaged
+ copies of a file.
* The lzip format is as simple as possible (but not simpler). The lzip
manual provides the source code of a simple decompressor along with a
@@ -54,9 +53,8 @@ makes it safer than compressors returning ambiguous warning values (like
gzip) when it is used as a back end for other programs like tar or zutils.
Clzip automatically uses for each file the largest dictionary size that does
-not exceed neither the file size nor the limit given. Keep in mind that the
-decompression memory requirement is affected at compression time by the
-choice of dictionary size limit.
+not exceed neither the file size nor the limit given. The dictionary size
+used for decompression is the same dictionary size used for compression.
The amount of memory required for compression is about 1 or 2 times the
dictionary size limit (1 if input file size is less than dictionary size
@@ -125,15 +123,15 @@ definition of Markov chains), G.N.N. Martin (for the definition of range
encoding), Igor Pavlov (for putting all the above together in LZMA), and
Julian Seward (for bzip2's CLI).
-Clzip uses Arg_parser for command-line argument parsing:
-http://www.nongnu.org/arg-parser/arg_parser.html
-
LANGUAGE NOTE: Uncompressed = not compressed = plain data; it may never have
been compressed. Decompressed is used to refer to data which have undergone
the process of decompression.
+Clzip uses Arg_parser for command-line argument parsing:
+http://www.nongnu.org/arg-parser/arg_parser.html
+
-Copyright (C) 2010-2024 Antonio Diaz Diaz.
+Copyright (C) 2010-2025 Antonio Diaz Diaz.
This file is free documentation: you have unlimited permission to copy,
distribute, and modify it.