It is quite fair that the development bitstream format, now version 7, changes arbitrarily and without ability to read previous development formats. But I think it's reasonable to restore the ability to read earlier released bitstream formats as soon as breaking changes are introduced during development -- instead of postponing that work to a later time before the next stable release. In the present case it's a very simple change so I can't see any good reason not to do it now (or even better if it had been done as part of the large 4aca6a6 commit of course).
Sample reproduction of regression (note junk output in the last characters):
$ head -1 enwik8 | kanzi253 -c -t none -e tpaq | kanzi -d | cat -A;echo
<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.3/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.3/ http://www.mediawiki.org/xml/export-0.3.xsd" version="F_^U*^RM-.@M-^EM-"M-y+M-7M-mlM-QrfM-1U^O
See attached patch for the simple fix. After that it can again read all of my old files compressed with kanzi 2.5.1.
0001-Restore-ability-to-read-bitstream-v6-TPAQ-X-data.patch.txt
It is quite fair that the development bitstream format, now version 7, changes arbitrarily and without ability to read previous development formats. But I think it's reasonable to restore the ability to read earlier released bitstream formats as soon as breaking changes are introduced during development -- instead of postponing that work to a later time before the next stable release. In the present case it's a very simple change so I can't see any good reason not to do it now (or even better if it had been done as part of the large 4aca6a6 commit of course).
Sample reproduction of regression (note junk output in the last characters):
See attached patch for the simple fix. After that it can again read all of my old files compressed with kanzi 2.5.1.
0001-Restore-ability-to-read-bitstream-v6-TPAQ-X-data.patch.txt