Sync autogenerated files #noupdate

Author: github-actions[bot]

doc/html/NON-AUTOTOOLS-BUILD.txt

@@ -171,7 +171,7 @@ example.
      src/config.h) . Compile src/pcre2test.c; don't forget -DHAVE_CONFIG_H if
      necessary, but do NOT define PCRE2_CODE_UNIT_WIDTH. Then link with the
      appropriate library/ies. If you compiled an 8-bit library, pcre2test also
-     needs the pcre2posix wrapper library.
+     needs the pcre2posix wrapper library when linking.
 
  (9) Run pcre2test on the testinput files in the testdata directory, and check
      that the output matches the corresponding testoutput files. There are

doc/html/pcre2api.html

@@ -1374,7 +1374,7 @@ <h2><a name="SEC19" href="#TOC1">CHECKING BUILD-TIME OPTIONS</a></h2>
 <pre>
   PCRE2_CONFIG_JITTARGET
 </pre>
-The <i>where</i> argument should point to a buffer that is at least 48 code
+The <i>where</i> argument should point to a buffer that is at least 64 code
 units long. (The exact length required can be found by calling
 <b>pcre2_config()</b> with <b>where</b> set to NULL.) The buffer is filled with a
 string that contains the name of the architecture for which the JIT compiler is
@@ -4614,7 +4614,7 @@ <h2><a name="SEC43" href="#TOC1">AUTHOR</a></h2>
 </p>
 <h2><a name="SEC44" href="#TOC1">REVISION</a></h2>
 <p>
-Last updated: 19 July 2025
+Last updated: 05 October 2025
 <br>
 Copyright &copy; 1997-2024 University of Cambridge.
 <br>

doc/html/pcre2build.html

@@ -157,8 +157,8 @@ <h2><a name="SEC5" href="#TOC1">UNICODE AND UTF SUPPORT</a></h2>
 0x10ffff in the strings that they handle. Unicode support also gives access to
 the Unicode properties of characters, using pattern escapes such as \P, \p,
 and \X. Only the general category properties such as <i>Lu</i> and <i>Nd</i>,
-script names, and some bi-directional properties are supported. Details are
-given in the
+script names, and some bi-directional and binary properties are supported.
+Details are given in the
 <a href="pcre2pattern.html"><b>pcre2pattern</b></a>
 documentation.
 </p>
@@ -172,8 +172,8 @@ <h2><a name="SEC6" href="#TOC1">DISABLING THE USE OF \C</a></h2>
 <p>
 The \C escape sequence, which matches a single code unit, even in a UTF mode,
 can cause unpredictable behaviour because it may leave the current matching
-point in the middle of a multi-code-unit character. The application can lock it
-out by setting the PCRE2_NEVER_BACKSLASH_C option when calling
+point in the middle of a multi-code-unit character. The application can lock
+it out by setting the PCRE2_NEVER_BACKSLASH_C option when calling
 <b>pcre2_compile()</b>. There is also a build-time option
 <pre>
   --enable-never-backslash-C
@@ -516,7 +516,7 @@ <h2><a name="SEC18" href="#TOC1">PCRE2TEST OPTION FOR LIBREADLINE SUPPORT</a></h
 If your environment has not been set up so that an appropriate library is
 automatically included, you may need to add something like
 <pre>
-  LIBS="-ncurses"
+  LIBS="-lncurses"
 </pre>
 immediately before the <b>configure</b> command.
 </p>

doc/pcre2.txt

@@ -1364,7 +1364,7 @@ CHECKING BUILD-TIME OPTIONS
 
          PCRE2_CONFIG_JITTARGET
 
-       The  where  argument  should point to a buffer that is at least 48 code
+       The  where  argument  should point to a buffer that is at least 64 code
        units long.  (The  exact  length  required  can  be  found  by  calling
        pcre2_config()  with  where  set  to NULL.) The buffer is filled with a
        string that contains the name of the architecture  for  which  the  JIT
@@ -4410,11 +4410,11 @@ AUTHOR
 
 REVISION
 
-       Last updated: 19 July 2025
+       Last updated: 05 October 2025
        Copyright (c) 1997-2024 University of Cambridge.
 
 
-PCRE2 10.47-DEV                  19 July 2025                      PCRE2API(3)
+PCRE2 10.47-DEV                 05 October 2025                    PCRE2API(3)
 ------------------------------------------------------------------------------
 
 
@@ -4538,8 +4538,8 @@ UNICODE AND UTF SUPPORT
        0x10ffff in the strings that they handle. Unicode  support  also  gives
        access  to  the Unicode properties of characters, using pattern escapes
        such as \P, \p, and \X. Only the general category properties such as Lu
-       and Nd, script names, and some bi-directional properties are supported.
-       Details are given in the pcre2pattern documentation.
+       and Nd, script names, and some bi-directional and binary properties are
+       supported.  Details are given in the pcre2pattern documentation.
 
        Pattern escapes such as \d and \w do not by default make use of Unicode
        properties. The application can request that they  do  by  setting  the
@@ -4906,7 +4906,7 @@ PCRE2TEST OPTION FOR LIBREADLINE SUPPORT
        If your environment has not been set up so that an appropriate  library
        is automatically included, you may need to add something like
 
-         LIBS="-ncurses"
+         LIBS="-lncurses"
 
        immediately before the configure command.