X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;f=doc%2Ffunctions.texi;h=f89a7f83a0c903ebc9033f2a8a1f63e1cdcfc863;hb=d7b344a2c6c70623de8fcdac7d129a4a2bad53e2;hp=d164d2483310ab92cf3a9f2299ad45acfc3ae6d1;hpb=a897449aaae8e6c051f3b9daaf984de5c5e092f3;p=gnulib.git

diff --git a/doc/functions.texi b/doc/functions.texi
index d164d2483..f89a7f83a 100644
--- a/doc/functions.texi
+++ b/doc/functions.texi
@@ -152,8 +152,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines this function so that
 it is POSIX compliant.
 
-On Windows, this function doesn't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item fputc
 @itemx fputs
@@ -465,8 +466,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines this function so that
 it is POSIX compliant.
 
-On Windows, this function doesn't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item pthread_create
 On Linux/glibc systems before the advent of NPTL, signals could only be
@@ -634,8 +636,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines this function so that
 it is POSIX compliant.
 
-On Windows, this function doesn't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item socket
 On BeOS, the descriptors returned by the @code{socket} function can not be used
@@ -648,8 +651,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines this function so that
 it is POSIX compliant.
 
-On Windows, this function doesn't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item sscanf
 On Windows systems (excluding Cygwin), this function does not set @code{errno}
@@ -786,8 +790,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines this function so that
 it is POSIX compliant.
 
-On Windows, this function doesn't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item vfscanf
 On Windows systems (excluding Cygwin), this function does not set @code{errno}
@@ -804,8 +809,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines these functions so
 that they are POSIX compliant.
 
-On Windows, these functions don't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item vscanf
 @item vsscanf