* later. Also, chunk sizes larger than <c>2^26</c> are not compatible
* with the Microsoft implementation.
*
- * wimlib's LZMS compressor is currently faster but will usually not
- * compress as much as the implementation in Microsoft's WIMGAPI
- * (Windows 8.1).
+ * wimlib's LZMS compressor will, with the default settings, usually
+ * produce a better compression ratio, and work more quickly, than the
+ * implementation in Microsoft's WIMGAPI (as of Windows 8.1). There is
+ * limited support for non-default compression levels, but compression
+ * will be noticably faster if you choose a level < 35.
*
* If using wimlib_create_compressor() to create an LZMS compressor
* directly, the @p max_block_size parameter may be any positive value
- * up to and including <c>1180427429</c>.
+ * up to and including <c>2^30</c>.
*/
WIMLIB_COMPRESSION_TYPE_LZMS = 3,
};
* all streams recompressed in solid mode.
*
* Currently, new solid resources will, by default, be written using LZMS
- * compression with 32 MiB (33554432 byte) chunks. Use
+ * compression with 64 MiB (67108864 byte) chunks. Use
* wimlib_set_output_pack_compression_type() and/or
* wimlib_set_output_pack_chunk_size() to change this. This is independent of
* the WIM's main compression type and chunk size; you can have a WIM that
* Therefore, it is a compressor-only parameter and does not need to be
* passed to the decompressor.
* <br/>
- * Since wimlib v1.7.5, this parameter can be OR-ed with the flag
+ * Since wimlib v1.8.0, this parameter can be OR-ed with the flag
* ::WIMLIB_COMPRESSOR_FLAG_DESTRUCTIVE. This creates the compressor in a
* mode where it is allowed to modify the input buffer. Specifically, in
* this mode, if compression succeeds, the input buffer may have been