Re: ffmpeg documentation no longer builds after Texinfo 7.1 (due to --init-file=)

2024-01-28 Thread Patrice Dumas
On Sun, Jan 28, 2024 at 12:16:42AM +, Gavin Smith wrote: > > If there is still a customization variable to access for this, then > > I don't see why the name has to be changed. I haven't had any new thoughts > > on this since my previous emails on the topic, I'm afraid. I remember > > that

Re: Customization variable to disable Unicode collation?

2024-01-28 Thread Patrice Dumas
On Sun, Jan 28, 2024 at 08:15:33PM +, Gavin Smith wrote: > Below is a patch to introduce a new variable to avoid using the > Unicode::Collate module. Turning the module off shortens run times by > about 5% (depending on the size of indices in the document). > > Users can use this if they

Re: Customization variable to disable Unicode collation?

2024-01-28 Thread Patrice Dumas
On Sun, Jan 28, 2024 at 08:52:02PM +, Gavin Smith wrote: > On Sun, Jan 28, 2024 at 09:25:38PM +0100, Patrice Dumas wrote: > > On Sun, Jan 28, 2024 at 08:15:33PM +, Gavin Smith wrote: > > > Below is a patch to introduce a new variable to avoid using the > > > Unicode::Collate module.

Re: ffmpeg documentation no longer builds after Texinfo 7.1 (due to --init-file=)

2024-01-28 Thread Patrice Dumas
On Sun, Jan 28, 2024 at 08:49:36PM +, Gavin Smith wrote: > > I like get_build_constant or get_build_configuration_value. I couldn't > think of an alternative to the word "build" to represent a certain > installed version of Texinfo but there might be one. Let's go with get_build_constant,

Re: Customization variable to disable Unicode collation?

2024-01-28 Thread Gavin Smith
On Sun, Jan 28, 2024 at 09:25:38PM +0100, Patrice Dumas wrote: > On Sun, Jan 28, 2024 at 08:15:33PM +, Gavin Smith wrote: > > Below is a patch to introduce a new variable to avoid using the > > Unicode::Collate module. Turning the module off shortens run times by > > about 5% (depending on

Re: ffmpeg documentation no longer builds after Texinfo 7.1 (due to --init-file=)

2024-01-28 Thread Patrice Dumas
On Sat, Jan 27, 2024 at 05:55:24PM +, Gavin Smith wrote: > The get_constant function has been recently added but I think the name of > this is too generic. Any idea on another name? -- Pat

Customization variable to disable Unicode collation?

2024-01-28 Thread Gavin Smith
Below is a patch to introduce a new variable to avoid using the Unicode::Collate module. Turning the module off shortens run times by about 5% (depending on the size of indices in the document). Users can use this if they don't find texi2any fast enough, if they don't care about having the

Re: ffmpeg documentation no longer builds after Texinfo 7.1 (due to --init-file=)

2024-01-28 Thread Gavin Smith
On Sun, Jan 28, 2024 at 09:13:21PM +0100, Patrice Dumas wrote: > On Sat, Jan 27, 2024 at 05:55:24PM +, Gavin Smith wrote: > > The get_constant function has been recently added but I think the name of > > this is too generic. > > Any idea on another name? It reminds me of the output of perl

texinfo does not compile without libintl.h even though configure checks for it

2024-01-28 Thread Erik A Johnson
Without libintl.h, tp/Texinfo/XS/parsetexi/api.c does not compile -- even though configure tests for libintl.h. In api.c, is the line #include actually needed? (Commenting that line out in texinfo-7.1 allows it to compile, complete tests, etc. on macOS Sonoma 14.2.1.)

Re: texinfo does not compile without libintl.h even though configure checks for it

2024-01-28 Thread Gavin Smith
On Mon, Jan 29, 2024 at 01:10:52AM +, Erik A Johnson wrote: > Without libintl.h, tp/Texinfo/XS/parsetexi/api.c does not compile -- even > though configure tests for libintl.h. In api.c, is the line > > #include > > actually needed? (Commenting that line out in texinfo-7.1 allows it