Fixed a minor compatibility issue with the LZMS compressor and
decompressor. This is *not* the default compression type and was only
- introduced in v1.6.0. In the unlikely event that you created a
+ introduced in v1.6.0. In the unlikely event that you created an
LZMS-compressed WIM with v1.6.0 and a checksum error is reported when
applying it with v1.6.1, decompress it with v1.6.0 then compress it with
v1.6.1.
archives. wimlib includes its own compression codecs and does not use the
compression API available on some versions of Windows. The below table provides
the results (file size, in bytes, and time to create, in seconds) of capturing a
-WIM containing a x86 Windows PE image, using various compression types and
+WIM containing an x86 Windows PE image, using various compression types and
options. When applicable, the results with the equivalent Microsoft
implementation in WIMGAPI, which is the library used by ImageX and Dism, are
included.
* will not be valid. */
WIMLIB_PROGRESS_MSG_WRITE_METADATA_BEGIN,
- /** Confirms that the metadata resource for each image has successfully
- * been writen to the WIM. @p info will not be valid. */
+ /** Confirms that per-image metadata has been successfully been written
+ * to the WIM file. @p info will not be valid. This message is paired
+ * with a preceding ::WIMLIB_PROGRESS_MSG_WRITE_METADATA_BEGIN message.
+ */
WIMLIB_PROGRESS_MSG_WRITE_METADATA_END,
/** wimlib_overwrite() has successfully renamed the temporary file to
/** An integrity table is being calculated for the WIM being written.
* @p info will point to ::wimlib_progress_info.integrity. This message
- * is only received (and may be received many times) when a WIM is being
- * written with the flag ::WIMLIB_WRITE_FLAG_CHECK_INTEGRITY. */
+ * is only received (and may be received many times) when a WIM file is
+ * being written with the flag ::WIMLIB_WRITE_FLAG_CHECK_INTEGRITY. */
WIMLIB_PROGRESS_MSG_CALC_INTEGRITY,
/** Reserved. */
/** For wimlib_extract_paths() and wimlib_extract_pathlist() only: Do not
* preserve the directory structure of the archive when extracting --- that is,
- * place each extracted files or directory tree directly in the target
- * directory. */
+ * place each extracted file or directory tree directly in the target directory.
+ */
#define WIMLIB_EXTRACT_FLAG_NO_PRESERVE_DIR_STRUCTURE 0x00200000
/** @} */
*
* As of wimlib v1.6.1, this function is deprecated in favor of
* wimlib_extract_paths() because wimlib_extract_paths() is easier to use and
- * usually more efficient.
+ * more efficient.
*
* Notes: wimlib_extract_files() does not support the
* ::WIMLIB_EXTRACT_FLAG_GLOB_PATHS flag, and
struct list_head *prev, *cur;
/* Can't use list_for_each_entry() because a call to
- * dentry_calculate_extraction_name() may the current dentry and its
- * children from the list. */
+ * dentry_calculate_extraction_name() may delete the current dentry and
+ * its children from the list. */
prev = dentry_list;
for (;;) {