https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=ccabeae4e3c684945f402e42e102cb976065ca2e
commit ccabeae4e3c684945f402e42e102cb976065ca2e Author: Kenneth Nellis <kenneth.nel...@conduent.com> Date: Tue Feb 14 09:46:56 2017 +0100 Improve wording on special characters Signed-off-by: Corinna Vinschen <cori...@vinschen.de> Diff: --- 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 0192fc2..bc4b044 100644 --- a/winsup/doc/specialnames.xml +++ b/winsup/doc/specialnames.xml @@ -79,7 +79,8 @@ in the Win32 API:</para> <para>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.</para> +(the "Private use area") when creating or accessing files by adding 0xf000 +to the forbidden characters' code points.</para> <para>The backslash has to be exempt from this conversion, because Cygwin accepts Win32 filenames including backslashes as path separators on input.