Documentation patch: Clarify Cygwin's support for Win32 paths

[Ken Brown]

The attached patch is the one promised in

   https://www.cygwin.com/ml/cygwin/2016-08/msg00431.html

Ken
-------------- next part --------------
From e46d88d4141737f7f75ec1fb60b6e404f598a965 Mon Sep 17 00:00:00 2001
From: Ken Brown <kbrown@cornell.edu>
Date: Tue, 23 Aug 2016 13:24:49 -0400
Subject: [PATCH] Clarify Cygwin's support for Win32 paths

See https://www.cygwin.com/ml/cygwin/2016-08/msg00431.html.
---
 winsup/doc/pathnames.xml | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/winsup/doc/pathnames.xml b/winsup/doc/pathnames.xml
index 3c0bdc1..6f9fefa 100644
--- a/winsup/doc/pathnames.xml
+++ b/winsup/doc/pathnames.xml
@@ -6,15 +6,18 @@
 
 <sect2 id="pathnames-intro"><title>Introduction</title>
 
-<para>Cygwin supports both POSIX- and Win32-style paths.  Directory
+<para>The Cygwin DLL supports both POSIX- and Win32-style paths.  Directory
 delimiters may be either forward slashes or backslashes.  Paths using
 backslashes or starting with a drive letter are always handled as
 Win32 paths.  POSIX paths must only use forward slashes as delimiter,
 otherwise they are treated as Win32 paths and file access might fail
 in surprising ways.</para>
 
-<note><para>The usage of Win32 paths, though possible, is deprecated,
-since it circumvents important internal path handling mechanisms. 
+<note><para>Although the Cygwin DLL supports Win32 paths, not all
+Cygwin applications support them.  Moreover, the usage of Win32 paths
+circumvents important internal path handling mechanisms.  This usage
+is therefore strongly deprecated and may be removed in a future
+release of Cygwin.
 See <xref linkend="pathnames-win32"></xref> and
 <xref linkend="pathnames-win32-api"></xref> for more information.
 </para></note>
@@ -451,11 +454,12 @@ filesystem borders by commands like <command>find -xdev</command>.</para>
 
 <sect2 id="pathnames-win32"><title>Using native Win32 paths</title>
 
-<para>Using native Win32 paths in Cygwin, while possible, is generally
+<para>Using native Win32 paths in Cygwin, while often possible, is generally
 inadvisable.  Those paths circumvent all internal integrity checking and
 bypass the information given in the Cygwin mount table.</para>
 
-<para>The following paths are treated as native Win32 paths in Cygwin:</para>
+<para>The following paths are treated as native Win32 paths by the
+Cygwin DLL (but not necessarily by Cygwin applications):</para>
 
 <itemizedlist spacing="compact">
   <listitem>
-- 
2.8.3