From ccabeae4e3c684945f402e42e102cb976065ca2e Mon Sep 17 00:00:00 2001 From: Kenneth Nellis Date: Tue, 14 Feb 2017 09:46:56 +0100 Subject: [PATCH] Improve wording on special characters Signed-off-by: Corinna Vinschen --- winsup/doc/specialnames.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/winsup/doc/specialnames.xml b/winsup/doc/specialnames.xml index 0192fc241..bc4b0440d 100644 --- a/winsup/doc/specialnames.xml +++ b/winsup/doc/specialnames.xml @@ -79,7 +79,8 @@ in the Win32 API: Cygwin can't fix this, but it has a method to workaround this restriction. All of the above characters, except for the backslash, are converted to special UNICODE characters in the range 0xf000 to 0xf0ff -(the "Private use area") when creating or accessing files. +(the "Private use area") when creating or accessing files by adding 0xf000 +to the forbidden characters' code points. The backslash has to be exempt from this conversion, because Cygwin accepts Win32 filenames including backslashes as path separators on input.