-Short (DOS) names for files
-.SH NTFS MODE (UNIX)
-This section documents how files are extracted directly to an NTFS volume image
-on UNIX. See \fBWINDOWS VERSION\fR for the corresponding documentation for the
-Windows version.
-.PP
-On UNIX, a special extraction mode is entered when \fITARGET\fR is a regular
-file or block device. If this is the case, \fITARGET\fR is interpreted as an
-NTFS volume and opened using libntfs-3g. If successful, the WIM image is
-extracted to the root of the NTFS volume in a special mode that preserves all
-information contained in the WIM image. \fIIMAGE\fR may not be "all" for this
-action.
-.PP
-The NTFS volume does not need to be empty, although it's expected that it be
-empty for the intended use cases. A new NTFS filesystem can be created using
-the \fBmkntfs\fR (8) command.
-.PP
-The NTFS extraction mode is not available if wimlib was compiled using the
-\fB--without-ntfs-3g\fR option.
-.PP
-Please note that the NTFS extraction mode is \fInot\fR entered if \fITARGET\fR
-is a directory, even if an NTFS filesystem is mounted on \fITARGET\fR. You must
-specify the NTFS volume itself (and it must be unmounted, and you must have
-permission to write to it).
-.PP
-In the NTFS extraction mode on UNIX, the following information will be extracted
-from the WIM image:
+Short (DOS) names for files.
+.IP \[bu]
+File creation timestamps.
+.PP
+Notes: Unsupported data and metadata is simply not extracted, but
+\fB@IMAGEX_PROGNAME@\fR will attempt to warn you when the contents of the WIM
+image can't be exactly represented when extracted. Last access and last
+modification timestamps are specified to 100 nanosecond granularity in the WIM
+file, but will only be extracted to the highest precision supported by the
+underlying operating system, C library, and filesystem. Compressed files will
+be extracted as uncompressed, while encrypted files will not be extracted at
+all.
+.SH NTFS VOLUME EXTRACTION (UNIX)
+This section documents how \fB@IMAGEX_PROGNAME@ apply\fR extracts a WIM image
+directly to an NTFS volume image on UNIX-like systems. See \fBDIRECTORY EXTRACTION
+(WINDOWS)\fR for the corresponding documentation for Windows.
+.PP
+As mentioned, \fB@IMAGEX_PROGNAME@\fR running on a UNIX-like system can apply a
+WIM image directly to an NTFS volume by specifying \fITARGET\fR as a regular file
+or block device containing an NTFS filesystem. The NTFS filesystem need not be
+empty, although it's expected that it be empty for the intended use cases. A
+new NTFS filesystem can be created using the \fBmkntfs\fR(8) command provided
+with \fBntfs-3g\fR.
+.PP
+In this NTFS volume extraction mode, the WIM image is extracted to the root of
+the NTFS volume in a way preserves almost all information contained in the WIM
+image. It therefore does not suffer from the limitations described in
+\fBDIRECTORY EXTRACTION (UNIX)\fR. This support relies on libntfs-3g to write
+to the NTFS volume and handle NTFS-specific and Windows-specific data.
+.PP
+Please note that this NTFS volume extraction mode is \fInot\fR entered if
+\fITARGET\fR is a directory, even if an NTFS filesystem is mounted on
+\fITARGET\fR. You must specify the NTFS volume itself (and it must be
+unmounted, and you must have permission to write to it).
+.PP
+This NTFS volume extraction mode attempts to extract as much information as
+possible, including: