summaryrefslogtreecommitdiffstats
path: root/doc/lziprecover.texi
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--doc/lziprecover.texi31
1 files changed, 22 insertions, 9 deletions
diff --git a/doc/lziprecover.texi b/doc/lziprecover.texi
index a460607..80d6eb4 100644
--- a/doc/lziprecover.texi
+++ b/doc/lziprecover.texi
@@ -6,19 +6,19 @@
@finalout
@c %**end of header
-@set UPDATED 1 July 2014
-@set VERSION 1.16-rc1
+@set UPDATED 29 August 2014
+@set VERSION 1.16
@dircategory Data Compression
@direntry
-* Lziprecover: (lziprecover). Data recovery tool for lzip files
+* Lziprecover: (lziprecover). Data recovery tool for the lzip format
@end direntry
@ifnothtml
@titlepage
@title Lziprecover
-@subtitle Data recovery tool for lzip files
+@subtitle Data recovery tool for the lzip format
@subtitle for Lziprecover version @value{VERSION}, @value{UPDATED}
@author by Antonio Diaz Diaz
@@ -47,8 +47,7 @@ This manual is for Lziprecover (version @value{VERSION}, @value{UPDATED}).
@end menu
@sp 1
-Copyright @copyright{} 2009, 2010, 2011, 2012, 2013, 2014
-Antonio Diaz Diaz.
+Copyright @copyright{} 2009-2014 Antonio Diaz Diaz.
This manual is free documentation: you have unlimited permission
to copy, distribute and modify it.
@@ -87,6 +86,11 @@ Additionally lzip is copylefted, which guarantees that it will remain
free forever.
@end itemize
+A nice feature of the lzip format is that a corrupt byte is easier to
+repair the nearer it is from the beginning of the file. Therefore, with
+the help of lziprecover, losing an entire archive just because of a
+corrupt byte near the beginning is a thing of the past.
+
Lziprecover is able to recover or decompress files produced by any of
the compressors in the lzip family; lzip, plzip, minilzip/lzlib, clzip
and pdlzip.
@@ -287,7 +291,7 @@ forms of data corruption.
Bit-flip happens when one bit in the file is changed from 0 to 1 or vice
versa. It may be caused by bad RAM or even by natural radiation. I have
-seen a case of bit-flip in a file stored in an USB flash drive.
+seen a case of bit-flip in a file stored on an USB flash drive.
Repairing a file can take some time. Small files or files with the error
located near the beginning can be repaired in a few seconds. But
@@ -564,8 +568,17 @@ Test N-bit errors only, instead of testing all the 255 wrong values for
each byte. @samp{N-bit error} means any value differing from the
original value in N bit positions, not a value differing from the
original value in the bit position N.@*
-The number of N-bit errors per byte (N = 1 to 8) is: 8 28 56 70 56 28 8 1@*
-Examples of @var{range}: 1 1,2,3 1-4 1,3-5,8 1-3,5-8
+The number of N-bit errors per byte (N = 1 to 8) is:
+@w{8 28 56 70 56 28 8 1}
+
+@multitable {Examples of @var{range}} {1, 2, 3, 5, 6, 7 and 8}
+@item Examples of @var{range} @tab Tests errors of N-bit
+@item 1 @tab 1
+@item 1,2,3 @tab 1, 2 and 3
+@item 2-4 @tab 2, 3 and 4
+@item 1,3-5,8 @tab 1, 3, 4, 5 and 8
+@item 1-3,5-8 @tab 1, 2, 3, 5, 6, 7 and 8
+@end multitable
@item -p @var{bytes}
@itemx --position=@var{bytes}