JehanneOS/newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

* pathnames.sgml (pathnames-specialchars): Add control chars to the

Browse Source 
list.  Explain backslash exception.
This commit is contained in:
Corinna Vinschen 2009-10-09 11:19:18 +00:00
parent 9fa1c6420b
commit 220f363d20
2 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
winsup/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2009-10-09 Corinna Vinschen <corinna@vinschen.de>
* pathnames.sgml (pathnames-specialchars): Add control chars to the
list. Explain backslash exception.
2009-10-03 Dave Korn <dave.korn.cygwin@gmail.com>
* faq-using.xml (faq.using.bloda): Add Lenovo IPS Core Service.

9
winsup/doc/pathnames.sgml
View File

@ -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.</para>
<para>Some characters are disallowed in filenames on Windows filesystems:</para>
<para>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:</para>
<screen>
" * : &lt; &gt; ? | \
@ -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.</para>
<para>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.</para>
</sect2>
<sect2 id="pathnames-unusual">