8 The test suite is too incomplete.
10 If the memory usage limit is less than about 13 MiB, xz is unable to
11 automatically scale down the compression settings enough even though
12 it would be possible by switching from BT2/BT3/BT4 match finder to
15 The code to detect number of CPU cores doesn't count hyperthreading
16 as multiple cores. In context of xz, it probably should.
17 Hyperthreading is good at least with p7zip.
19 XZ Utils compress some files significantly worse than LZMA Utils.
20 This is due to faster compression presets used by XZ Utils, and
21 can often be worked around by using "xz --extreme". With some files
22 --extreme isn't enough though: it's most likely with files that
23 compress extremely well, so going from compression ratio of 0.003
24 to 0.004 means big relative increase in the compressed file size.
26 xz doesn't quote unprintable characters when it displays file names
27 given on the command line.
29 tuklib_exit() doesn't block signals => EINTR is possible.
31 SIGTSTP is not handled. If xz is stopped, the estimated remaining
32 time and calculated (de)compression speed won't make sense in the
33 progress indicator (xz --verbose).
39 xz doesn't support copying extended attributes, access control
40 lists etc. from source to target file.
42 Multithreaded compression:
43 - Reduce memory usage of the current method.
44 - Implement threaded match finders.
45 - Implement pigz-style threading in LZMA2.
47 Multithreaded decompression
49 Buffer-to-buffer coding could use less RAM (especially when
50 decompressing LZMA1 or LZMA2).
52 I/O library is not implemented (similar to gzopen() in zlib).
53 It will be a separate library that supports uncompressed, .gz,
54 .bz2, .lzma, and .xz files.
56 Check the first 0x00 byte of LZMA data.
58 Support changing lzma_options_lzma.mode with lzma_filters_update().
60 Support LZMA_FULL_FLUSH for lzma_stream_decoder() to stop at
61 Block and Stream boundaries.
63 lzma_strerror() to convert lzma_ret to human readable form?
64 This is tricky, because the same error codes are used with
65 slightly different meanings, and this cannot be fixed anymore.
71 Some tutorial is needed for liblzma. I have planned to write some
72 extremely well commented example programs, which would work as
73 a tutorial. I suppose the Doxygen tags are quite OK as a quick
74 reference once one is familiar with the liblzma API.
76 Document the LZMA1 and LZMA2 algorithms.