lziprecover/NEWS

Changes in version 1.20:

Splitting was broken for files larger than 64 KiB because of a bug
introduced in version 1.16.

The options "--dump-tdata", "--remove-tdata", and "--strip-tdata" have
been added to ease the management of metadata stored as trailing data:

  "--dump-tdata" dumps the trailing data (if any) of one or more regular
  files to standard output.

  "--remove-tdata" removes the trailing data from regular files in place.

  "--strip-tdata" copies one or more regular files to standard output,
  stripping the trailing data (if any) from each file.

The option '--loose-trailing', has been added.

The test used by lziprecover to discriminate trailing data from a corrupt
header in multimember or concatenated files has been improved to a
Hamming distance (HD) of 3, and the 3 bit flips must happen in different
magic bytes for the test to fail. As a consequence some kinds of files
no longer can be appended to a lzip file as trailing data unless the
'--loose-trailing' option is used when decompressing.
Lziprecover can be used to remove conflicting trailing data from a file.

The contents of a corrupt or truncated header found in a multimember
file is now shown, after the error message, in the same format as
trailing data.

The 'bits/byte' ratio has been replaced with the inverse compression
ratio in the output.

The progress of decompression is now shown at verbosity level 2 (-vv) or
higher.

Progress of decompression is only shown if stderr is a terminal.

A final diagnostic is now shown at verbosity level 1 (-v) or higher if
any file fails the test when testing multiple files.

In case of (de)compressed size mismatch, the stored size is now also
shown in hexadecimal to ease visual comparison.

The dictionary size is now shown at verbosity level 4 (-vvvv) when
decompressing or testing.