> Date: Mon, 19 Jan 2026 15:45:43 +0100 > From: [email protected] > Cc: [email protected], [email protected] > > On Mon, Jan 19, 2026 at 04:40:20PM +0200, Eli Zaretskii wrote: > > > Date: Mon, 19 Jan 2026 15:26:05 +0100 > > > From: [email protected] > > > Cc: [email protected], [email protected] > > > > > > It is less important as the Perl implementation is the one that will be > > > used by most users, but we propose the C implementation of texi2any too, > > > and I would like to know if it works on mingw. My gut feeling is that > > > it does not work because it cannot find the libraries it was linked > > > against, but there could be a good surprise. I would be interested > > > to know both if the tests in source work, and if it works after being > > > installed. > > > > > > As you know now, this means calling configure with > > > --enable-using-c-texi2any. > > > > Is it okay to delay this testing till the next pretest? > > Everything/anything is ok ;-).
OK (I presume the next pretest will come soon). And another question: when running the test suite, is it easy to switch between using ctexi2any and texi2any? It seems to me that just saying $ make check CONVERTER=texi2any one could run the test suite using the Perl implementation even if the package was configured with --enable-using-c-texi2any, is that right?
