From: Eric Biggers Date: Tue, 16 Aug 2016 06:55:51 +0000 (-0700) Subject: wimapply.1: fix documentation for valid Windows filenames X-Git-Tag: v1.10.0~3 X-Git-Url: https://wimlib.net/git/?p=wimlib;a=commitdiff_plain;h=5356aeb52cca00d53f7708398be6a29a25c2e2fd wimapply.1: fix documentation for valid Windows filenames * "must end with space or period" is not a restriction for NT APIs * control characters are forbidden --- diff --git a/doc/man1/wimlib-imagex-apply.1 b/doc/man1/wimlib-imagex-apply.1 index 688d74f0..7d7642b7 100644 --- a/doc/man1/wimlib-imagex-apply.1 +++ b/doc/man1/wimlib-imagex-apply.1 @@ -337,15 +337,15 @@ byte except '\\0' and \'/', so on a POSIX-compliant system this option will only have an effect in the unlikely case that the WIM image for some reason has a filename containing one of these characters. .IP "" -On Windows, filenames are case-insensitive(*), cannot include the characters -'/', \'\\0', '\\', ':', '*', '?', '"', '<', '>', or '|', and cannot end with a -space or period. Ordinarily, files in WIM images should meet these conditions -as well. However, it is not guaranteed, and in particular a WIM image captured -with \fBwimlib-imagex\fR on a POSIX-compliant system could contain such files. -By default, invalid names will be ignored, and if there are multiple names -differing only in case, one will be chosen to extract arbitrarily; however, with -\fB--include-invalid-names\fR, all names will be sanitized and extracted in some -form. +On Windows, filenames are case-insensitive(*), cannot include control +characters, and cannot include the characters '/', \'\\0', '\\', ':', '*', '?', +\'"', '<', '>', or '|'. Ordinarily, files in WIM images should meet these +conditions as well. However, it is not guaranteed, and in particular a WIM image +captured with \fBwimlib-imagex\fR on a POSIX-compliant system could contain such +files. By default, invalid names will be ignored, and if there are multiple +names differing only in case, one will be chosen to extract arbitrarily; +however, with \fB--include-invalid-names\fR, all names will be sanitized and +extracted in some form. .IP "" (*) Unless the ObCaseInsensitive setting has been set to 0 in the Windows registry, in which case certain software, including the Windows version of