From 220f363d20cf63e78887212d86fa966e794c8030 Mon Sep 17 00:00:00 2001 From: Corinna Vinschen Date: Fri, 9 Oct 2009 11:19:18 +0000 Subject: [PATCH] * pathnames.sgml (pathnames-specialchars): Add control chars to the list. Explain backslash exception. --- winsup/doc/ChangeLog | 5 +++++ winsup/doc/pathnames.sgml | 9 ++++++++- 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index c8655e97d..646d584bb 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,8 @@ +2009-10-09 Corinna Vinschen + + * pathnames.sgml (pathnames-specialchars): Add control chars to the + list. Explain backslash exception. + 2009-10-03 Dave Korn * faq-using.xml (faq.using.bloda): Add Lenovo IPS Core Service. diff --git a/winsup/doc/pathnames.sgml b/winsup/doc/pathnames.sgml index 527096fcb..cb8365b97 100644 --- a/winsup/doc/pathnames.sgml +++ b/winsup/doc/pathnames.sgml @@ -379,7 +379,10 @@ all of them are removed before the file is created. This restriction only affects native Win32 applications. Cygwin applications can create and access files with trailing dots and spaces without problems. -Some characters are disallowed in filenames on Windows filesystems: +Additionally, some characters are disallowed in filenames on Windows +filesystems. These forbidden characters are the ASCII control characters +from ASCII value 1 to 31, plus the following charcters which have a special +menaing in the Win32 API: " * : < > ? | \ @@ -390,6 +393,10 @@ 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 backslash has to be exempt from this conversion, because Cygwin +accepts Win32 filenames including backslashes as path separators on input. +Converting backslashes using the above method would make this impossible. + -- 2.43.5