From da3d07857e8877d884705832c5fd038f3e44751f Mon Sep 17 00:00:00 2001
From: Daniel Baumann <mail@daniel-baumann.ch>
Date: Sat, 7 Nov 2015 11:05:19 +0100
Subject: Merging upstream version 1.16.

Signed-off-by: Daniel Baumann <mail@daniel-baumann.ch>
---
 doc/lzip.info | 35 ++++++++++++++++++++---------------
 1 file changed, 20 insertions(+), 15 deletions(-)

(limited to 'doc/lzip.info')

diff --git a/doc/lzip.info b/doc/lzip.info
index c3324a5..a2d18bc 100644
--- a/doc/lzip.info
+++ b/doc/lzip.info
@@ -11,7 +11,7 @@ File: lzip.info,  Node: Top,  Next: Introduction,  Up: (dir)
 Lzip Manual
 ***********
 
-This manual is for Lzip (version 1.16-rc1, 30 June 2014).
+This manual is for Lzip (version 1.16, 26 August 2014).
 
 * Menu:
 
@@ -26,8 +26,7 @@ This manual is for Lzip (version 1.16-rc1, 30 June 2014).
 * Concept index::          Index of concepts
 
 
-   Copyright (C) 2008, 2009, 2010, 2011, 2012, 2013, 2014 Antonio Diaz
-Diaz.
+   Copyright (C) 2008-2014 Antonio Diaz Diaz.
 
    This manual is free documentation: you have unlimited permission to
 copy, distribute and modify it.
@@ -42,7 +41,7 @@ Lzip is a lossless data compressor with a user interface similar to the
 one of gzip or bzip2. Lzip is about as fast as gzip, compresses most
 files more than bzip2, and is better than both from a data recovery
 perspective. Lzip is a clean implementation of the LZMA
-(Lempel-Ziv-Markov chain-Algorithm) algorithm.
+(Lempel-Ziv-Markov chain-Algorithm) "algorithm".
 
    The lzip file format is designed for long-term data archiving, taking
 into account both data integrity and decoder availability:
@@ -63,6 +62,11 @@ into account both data integrity and decoder availability:
    * Additionally lzip is copylefted, which guarantees that it will
      remain free forever.
 
+   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.
+
    The member trailer stores the 32-bit CRC of the original data, the
 size of the original data and the size of the member. These values,
 together with the value remaining in the range decoder and the
@@ -77,7 +81,8 @@ uncompressed data.
 
    Lzip uses the same well-defined exit status values used by bzip2,
 which makes it safer than compressors returning ambiguous warning
-values (like gzip) when it is used as a back end for tar or zutils.
+values (like gzip) when it is used as a back end for other programs
+like tar or zutils.
 
    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
@@ -996,7 +1001,7 @@ public:
     pos( 0 ),
     stream_pos( 0 ),
     crc_( 0xFFFFFFFFU )
-    { buffer[dictionary_size-1] = 0; }		// prev_byte of first_byte
+    { buffer[dictionary_size-1] = 0; }		// prev_byte of first byte
 
   ~LZ_decoder() { delete[] buffer; }
 
@@ -1212,15 +1217,15 @@ Concept index
 
 Tag Table:
 Node: Top208
-Node: Introduction1055
-Node: Algorithm5733
-Node: Invoking lzip8491
-Node: File format14167
-Node: Stream format16715
-Node: Examples26147
-Node: Problems28104
-Node: Reference source code28634
-Node: Concept index42151
+Node: Introduction1022
+Node: Algorithm5992
+Node: Invoking lzip8750
+Node: File format14426
+Node: Stream format16974
+Node: Examples26406
+Node: Problems28363
+Node: Reference source code28893
+Node: Concept index42410
 
 End Tag Table
 
-- 
cgit v1.2.3