I did this:
> 2023-07-23 Bruno Haible <[email protected]>
>
> fnmatch: Work around bugs on FreeBSD, NetBSD, Solaris, Cygwin, Android.
This patch fixed also the Solaris 10 bug regarding the test case
fnmatch ("x?y", "x\360\237\230\213y", 0) == 0
So, let me update the doc.
2023-07-24 Bruno Haible <[email protected]>
fnmatch: Update doc regarding Solaris 10.
* doc/posix-functions/fnmatch.texi: Move the Solaris 10 bug description
to the "fixed by Gnulib" section.
diff --git a/doc/posix-functions/fnmatch.texi b/doc/posix-functions/fnmatch.texi
index 69560c33a6..ba76c45dd1 100644
--- a/doc/posix-functions/fnmatch.texi
+++ b/doc/posix-functions/fnmatch.texi
@@ -46,6 +46,12 @@
@c fnmatch ("x?y", "x\360\237\230\213y", 0) == 0
Android 13.
@item
+The @code{"?"} pattern character fails to match characters outside the
+Unicode BMP on some platforms:
+@c Failing test cases:
+@c fnmatch ("x?y", "x\360\237\230\213y", 0) == 0
+Solaris 10.
+@item
In the pattern, negated character ranges (such as @code{[!a-z]}) are not
supported on some platforms:
@c Failing test cases:
@@ -153,7 +159,7 @@
Unicode BMP on some platforms:
@c Failing test cases:
@c fnmatch ("x?y", "x\360\237\230\213y", 0) == 0
-Solaris 10, Cygwin 3.4.6,
+Cygwin 3.4.6,
@c Failing test cases:
@c fnmatch ("x?y", "x\360\237\230\213y", 0) == 0
@c fnmatch ("x[[:alnum:]]y", "x\360\220\214\260y", 0) == 0
