On Tue, Nov 12, 2024 at 04:27:21PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Sun, 10 Nov 2024 19:21:57 +
> > Cc: platform-test...@gnu.org
> >
> > A pretest distribution for the next Texinfo release (7.2) has been
> > uploaded to
> >
> > https://alpha.gnu.org/gnu/texinfo/tex
> Date: Fri, 15 Nov 2024 21:12:42 +0100
> From: Patrice Dumas
>
> On Fri, Nov 15, 2024 at 05:01:35PM +, Gavin Smith wrote:
> > > My free time is severely limited, so I prefer to wait until the next
> > > pretest. But if that is too far away, I might try building a snapshot
> > > tarball, if
> From: Gavin Smith
> Date: Fri, 15 Nov 2024 17:01:35 +
> Cc: Patrice Dumas , bug-texinfo@gnu.org
>
> On Fri, Nov 15, 2024 at 09:44:15AM +0200, Eli Zaretskii wrote:
> > > > Let me know if you'd like me to provide more information or to test
> > > > some fixes.
> > >
> > > Could you please tr
On Fri, Nov 15, 2024 at 05:01:35PM +, Gavin Smith wrote:
> > My free time is severely limited, so I prefer to wait until the next
> > pretest. But if that is too far away, I might try building a snapshot
> > tarball, if you or Gavin can produce such a tarball. (I don't want to
> > try buildin
On Fri, Nov 15, 2024 at 06:56:24PM +, Gavin Smith wrote:
> However, I have not tested the tex-html tests as I don't have all the
> program installed on my computer to run them, so cannot be completely sure
> I updated them correctly. Hopefully someone else can check they work.
I checked and g
On Fri, Nov 15, 2024 at 07:29:20PM +, Gavin Smith wrote:
> Here are the non-ASCII file names left in the tar file, now the results
> files are all escaped:
>
> texinfo-7.1.91/tp/t/results/formats_encodings/accented_character_in_file_name/res_info/osé_utf8.info
> texinfo-7.1.91/tp/tests/encoded
On Thu, Nov 14, 2024 at 12:26:45AM +0100, Patrice Dumas wrote:
> On Wed, Nov 13, 2024 at 10:08:10PM +, Gavin Smith wrote:
> > I feel like this should be quite easy to achieve for the input
> > files, at least, as we already do something similar for an input
> > file with a Latin-1 name, which w
On Thu, Nov 14, 2024 at 08:03:42PM +, Gavin Smith wrote:
> I've written a Perl program to rename a list of files provided on
> standard input, using maintain/copy_change_file_name_encoding.pl as a
> starting point (this was not as simple for me as I thought it might be,
> as both directory and
On Fri, Nov 15, 2024 at 09:44:15AM +0200, Eli Zaretskii wrote:
> > > Let me know if you'd like me to provide more information or to test
> > > some fixes.
> >
> > Could you please try to see if MiscXS and XSParagraph compile now, and
> > also if the removal of many Gnulib modules done by Gavin lea
> Date: Thu, 14 Nov 2024 21:54:07 +0100
> From: Patrice Dumas
> Cc: Gavin Smith , bug-texinfo@gnu.org
>
> On Tue, Nov 12, 2024 at 04:27:21PM +0200, Eli Zaretskii wrote:
> > 3. Function redefinition warnings compiling MiscXS. Here's one example:
>
> MiscXS do not actually depends on Gnulib. All
On Thu, Nov 14, 2024 at 08:03:41PM +, Gavin Smith wrote:
> I've written a Perl program to rename a list of files provided on
> standard input, using maintain/copy_change_file_name_encoding.pl as a
> starting point (this was not as simple for me as I thought it might be,
> as both directory and
On Thu, Nov 14, 2024 at 08:05:20PM +, Gavin Smith wrote:
> On Thu, Nov 14, 2024 at 12:40:39AM +0100, Patrice Dumas wrote:
> > I think that you are right. It would be better if the jssrcdir file
> > was decoded (to UTF-8) as in convert/html_prepare_converter.c
> > parse_htmlxref_files using COM
On Tue, Nov 12, 2024 at 04:27:21PM +0200, Eli Zaretskii wrote:
> 3. Function redefinition warnings compiling MiscXS. Here's one example:
MiscXS do not actually depends on Gnulib. All the issues should be gone
with:
https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=fac78a49c9b51f4888ef1ac7
On Thu, Nov 14, 2024 at 12:40:39AM +0100, Patrice Dumas wrote:
> I think that you are right. It would be better if the jssrcdir file
> was decoded (to UTF-8) as in convert/html_prepare_converter.c
> parse_htmlxref_files using COMMAND_LINE_ENCODING before being output
> in the error message.
I've
On Thu, Nov 14, 2024 at 11:44:36AM +0200, Eli Zaretskii wrote:
> > Date: Thu, 14 Nov 2024 10:07:11 +0100
> > From: Patrice Dumas
> >
> > On Thu, Nov 14, 2024 at 07:42:02AM +, Gavin Smith wrote:
> > > On Thu, Nov 14, 2024 at 08:47:25AM +0200, Eli Zaretskii wrote:
> > > > I'm not sure I follow:
> Date: Thu, 14 Nov 2024 15:07:34 +0100
> From: Patrice Dumas
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
>
> What is your Perl version? Normally configure should have detected if
> it is not recent enough, so I do not expect it to be very important, but
> who knows.
5.20.1, quite old.
On Thu, Nov 14, 2024 at 11:56:11AM +0100, Patrice Dumas wrote:
> On Tue, Nov 12, 2024 at 04:27:21PM +0200, Eli Zaretskii wrote:
> > 4. Compilation error in api_to_perl.c:
> >
> > In file included from D:/usr/Perl/lib/CORE/perl.h:5056,
> > from main/api_to_perl.c:23:
> >
On Thu, Nov 14, 2024 at 01:40:52PM +0200, Eli Zaretskii wrote:
> Yes, but which header exactly causes the syntax error? I don't see
> vTHX mentioned in any header in the Texinfo tree, except this:
>
>tp/Texinfo/XS/ppport.h:10353:vTHX|5.006000||Viu
>
> Could this cause the problem? (I don't
> Date: Thu, 14 Nov 2024 11:56:11 +0100
> From: Patrice Dumas
> Cc: Gavin Smith , bug-texinfo@gnu.org
>
> On Tue, Nov 12, 2024 at 04:27:21PM +0200, Eli Zaretskii wrote:
> > 4. Compilation error in api_to_perl.c:
> >
> > In file included from D:/usr/Perl/lib/CORE/perl.h:5056,
> >
On Tue, Nov 12, 2024 at 04:27:21PM +0200, Eli Zaretskii wrote:
> 4. Compilation error in api_to_perl.c:
>
> In file included from D:/usr/Perl/lib/CORE/perl.h:5056,
> from main/api_to_perl.c:23:
> D:/usr/Perl/lib/CORE/embedvar.h:58:23: error: expected ')' before '->'
> Date: Thu, 14 Nov 2024 10:07:11 +0100
> From: Patrice Dumas
>
> On Thu, Nov 14, 2024 at 07:42:02AM +, Gavin Smith wrote:
> > On Thu, Nov 14, 2024 at 08:47:25AM +0200, Eli Zaretskii wrote:
> > > I'm not sure I follow: do you intend to use "int\xc3\xa9rnal.txt" as
> > > an actual file name on
On Thu, Nov 14, 2024 at 07:42:02AM +, Gavin Smith wrote:
> On Thu, Nov 14, 2024 at 08:47:25AM +0200, Eli Zaretskii wrote:
> > I'm not sure I follow: do you intend to use "int\xc3\xa9rnal.txt" as
> > an actual file name on disk? In that case, please note that a
> > backslash cannot be part of a
On Thu, Nov 14, 2024 at 08:47:25AM +0200, Eli Zaretskii wrote:
> > For the reference test results, this does not work, as these results
> > are checked in a fixed location in srcdir.
> >
> > The easiest solution that comes to mind is to post-process the test
> > results to escape file names. So i
On Thu, Nov 14, 2024 at 12:26:45AM +0100, Patrice Dumas wrote:
> > For the reference test results, this does not work, as these results
> > are checked in a fixed location in srcdir.
> >
> > The easiest solution that comes to mind is to post-process the test
> > results to escape file names. So i
> From: Gavin Smith
> Date: Wed, 13 Nov 2024 22:08:10 +
> Cc: bug-texinfo@gnu.org
>
> On Wed, Nov 13, 2024 at 10:37:37PM +0200, Eli Zaretskii wrote:
> > Can they be included as some kind or archive? Like shar file, for
> > example? Then users on Posix systems could unpack that before runnin
On Wed, Nov 13, 2024 at 10:37:37PM +0200, Eli Zaretskii wrote:
> Can they be included as some kind or archive? Like shar file, for
> example? Then users on Posix systems could unpack that before running
> the test suite, and users of Windows won't.
>
> Or some other similar solution; removing th
On Wed, Nov 13, 2024 at 08:00:34PM +, Gavin Smith wrote:
> On Tue, Nov 12, 2024 at 09:35:24PM +, Gavin Smith wrote:
> > I can't see how it can be that complicated to call fopen/fread/fwrite
> > ourselves to copy the file. These are all completely standard library
> > functions. I can have
On Wed, Nov 13, 2024 at 10:08:10PM +, Gavin Smith wrote:
> I feel like this should be quite easy to achieve for the input
> files, at least, as we already do something similar for an input
> file with a Latin-1 name, which we place in a directory in the
> build directory ("built_input"). This
> From: Gavin Smith
> Date: Wed, 13 Nov 2024 20:16:29 +
> Cc: bug-texinfo@gnu.org
>
> On Tue, Nov 12, 2024 at 04:27:21PM +0200, Eli Zaretskii wrote:
> > Btw, an additional annoyance when unpacking the tarball of this
> > pretest is that it creates files with non-ASCII characters that any
> >
On Tue, Nov 12, 2024 at 04:27:21PM +0200, Eli Zaretskii wrote:
> Btw, an additional annoyance when unpacking the tarball of this
> pretest is that it creates files with non-ASCII characters that any
> Windows commands cannot delete. I needed to look for a suitable tool
> which would be up to the j
On Tue, Nov 12, 2024 at 09:35:24PM +, Gavin Smith wrote:
> I can't see how it can be that complicated to call fopen/fread/fwrite
> ourselves to copy the file. These are all completely standard library
> functions. I can have a go at implementing this in the next couple of
> days.
My work on
On Tue, Nov 12, 2024 at 09:50:27PM +0100, Patrice Dumas wrote:
> On Tue, Nov 12, 2024 at 08:09:58PM +, Gavin Smith wrote:
> >
> > convert/convert_html.c:23:10: fatal error: copy-file.h: No such file or
> > directory
> >23 | #include "copy-file.h"
> > | ^
> > com
On Tue, Nov 12, 2024 at 08:09:58PM +, Gavin Smith wrote:
>
> convert/convert_html.c:23:10: fatal error: copy-file.h: No such file or
> directory
>23 | #include "copy-file.h"
> | ^
> compilation terminated.
>
> Note this is for copying the JavaScript files with
On Tue, Nov 12, 2024 at 07:05:42PM +, Gavin Smith wrote:
> I do not remember removing a gnulib module being this difficult.
I worked around it by copying the command from gnulib/lib/Makefile.am
and removing the "copy-file" line:
../../../../gnulib/gnulib-tool --import \
--lib=libgnu \
--s
> From: Gavin Smith
> Date: Tue, 12 Nov 2024 19:05:41 +
> Cc: bug-texinfo@gnu.org
>
> Add gnulib copy-file module
>
> * tp/Texinfo/XS:
> Run "gnulib-tool --add-import copy-file"
>
> Importing this module brought in many files.
Yes, I was very surprised to see what seemed li
On Tue, Nov 12, 2024 at 04:27:21PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Sun, 10 Nov 2024 19:21:57 +
> > Cc: platform-test...@gnu.org
> >
> > A pretest distribution for the next Texinfo release (7.2) has been
> > uploaded to
> >
> > https://alpha.gnu.org/gnu/texinfo/tex
36 matches
Mail list logo