+A WIM image is an independent directory tree in the WIM file. A WIM file may
+contain any number of separate images. However, files are stored only one time
+in the entire WIM, regardless of how many images the file appears in.
+.PP
+\fISOURCE\fR specifies the location of the files to create the new WIM image
+from. If \fISOURCE\fR is a directory, the WIM image is captured from that
+directory. Alternatively, if the \fB--source-list\fR option is given,
+\fISOURCE\fR is interpreted as a file that itself provides a list of
+files and directories to include in the new WIM image. Still
+alternatively, only on UNIX builds of wimlib, if \fISOURCE\fR is a
+regular file or block device, it is interpreted as an NTFS volume from
+which a WIM image is to be captured.
+.PP
+\fIIMAGE_NAME\fR and \fIIMAGE_DESCRIPTION\fR specify the name and description of
+the new image. If \fIIMAGE_NAME\fR is not given, it is taken to be the same as
+the base name of \fISOURCE\fR. If \fIIMAGE_DESCRIPTION\fR is not given, no
+description is given to the new image.
+.SH NORMAL MODE (UNIX)
+This section documents how files are captured from a directory on UNIX. See
+\fBWINDOWS VERSION\fR for the corresponding documentation for the Windows
+version.
+.PP
+On UNIX, the "normal" image capture mode is entered when \fISOURCE\fR specifies
+a directory. The WIM image will be captured from the directory tree rooted at
+this directory. The directory may be on any type of filesystem.
+.PP
+In this mode, the following information is captured from the directory tree:
+.IP \[bu] 4
+The "normal" name and contents of each file and directory
+.IP \[bu]
+File and directory creation, access, and modification timestamps to the nearest
+100 nanoseconds, if supported by the underlying filesystem
+.IP \[bu]
+Hard links and symbolic links
+.PP
+However, in this mode, the following information is \fInot\fR captured from the
+directory tree:
+.IP \[bu] 4
+UNIX file owners, groups, and modes. The resulting WIM image will contain no
+security information (file permissions). (Exception: see the \fB--unix-data\fR
+option.)
+.IP \[bu]
+Extended attributes.
+.SH NTFS MODE (UNIX)
+This section documents how files are captured from an NTFS volume image on UNIX.
+See \fBWINDOWS VERSION\fR for the corresponding documentation for the Windows
+version.
+.PP
+On UNIX, a special image capture mode is entered when \fISOURCE\fR is a regular
+file or block device. \fISOURCE\fR is interpreted as an NTFS volume and opened
+using libntfs-3g. If successful, a WIM image is captured containing the
+contents of the NTFS volume, including NTFS-specific data.
+.PP
+Please note that the NTFS image capture mode is \fInot\fR entered if
+\fISOURCE\fR is a directory, even if an NTFS filesystem is mounted on
+\fISOURCE\fR. You must specify the NTFS volume itself (and it must be
+unmounted, and you must have permission to read from it).
+.PP
+More specifically, in this mode, the following types of information are captured
+from the NTFS volume:
+.IP \[bu] 4
+All data streams of all files, including the un-named data stream as well as all
+named data streams.
+.IP \[bu]
+Reparse points, including symbolic links, junction points, and other reparse
+points.
+.IP \[bu]
+File and directory creation, access, and modification timestamps from NTFS
+inodes (these have a resolution of 100 nanoseconds).
+.IP \[bu]
+The security descriptor for each NTFS inode.
+.IP \[bu]
+File attribute flags.
+.IP \[bu]
+All names of all files, including names in the Win32 namespace, DOS namespace,
+Win32+DOS namespace, and POSIX namespace. This includes hard links.
+.SH WINDOWS VERSION
+The Windows versions of \fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@
+append\fR act similarly to the corresponding commands of Microsoft's ImageX.
+For best results, the directory being captured should be on an NTFS volume and
+you should be running with Administrator privileges; however, non-NTFS
+filesystems and running without Administrator privileges are also supported.
+.PP
+On Windows, \fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@ append\fR
+try to archive as much data as possible. This includes:
+.IP \[bu] 4
+All data streams of all files. This includes the default file contents, as well
+as named data streams if supported by the filesystem and if the version of
+Windows is Vista or later.
+.IP \[bu]
+Reparse points, including symbolic links, junction points, and other reparse
+points, if supported by the underlying filesystem. (Note: see
+\fB--rpfix\fR and \fB--norpfix\fR for documentation on how absolute symbolic
+links and junctions are captured.)
+.IP \[bu]
+File and directory creation, access, and modification timestamps to the nearest
+100 nanoseconds.
+.IP \[bu]
+Security descriptors, if supported by the filesystem and \fB--no-acls\fR is not
+specified. Furthermore, unless \fB--strict-acls\fR is specified, the security
+descriptor for individual files or directories may be omitted or only partially
+captured if the user does not have permission to read them.
+.IP \[bu]
+File attributes, including hidden, sparse, compressed, encrypted, etc.
+Encrypted files will be stored in encrypted form rather than in plain text.
+.IP \[bu]
+DOS names (8.3) names of files; however, the failure to read them is not
+considered an error condition.
+.IP \[bu]
+Hard links, excluding directory hard links (which aren't supposed to exist
+anyway).