Re: Build from git broken - missing gperf?

On Sun, Feb 04, 2024 at 07:59:37PM +, Gavin Smith wrote: > I can't build from commit 5154587461e (2024-02-04). It ends with the > errors: > > make[2]: Entering directory '/home/g/src/texinfo/GIT/tp/Texinfo/XS/gnulib/lib' > gperf -m 10 ./iconv_open-aix.gperf &g

Re: Build from git broken - missing gperf?

On Tue, Feb 06, 2024 at 07:13:09PM +0100, Patrice Dumas wrote: > On Mon, Feb 05, 2024 at 07:35:59PM +0000, Gavin Smith wrote: > > I don't know if uniconv/u8-conv-from-enc is a necessary module. It's > > not easy to find out how the module is used as the documentati

Re: `@unmacro` regression

On Sun, Feb 04, 2024 at 04:18:27PM +, Werner LEMBERG wrote: > Indeed, because it is not too an exotic feature. In LilyPond, we have > a bunch of smaller files that get included in a master document; every > file comprises a section of the document and essentially starts with > > ``` > @unmacr

Re: Segmentation fault with GNU texinfo 7.1

On Fri, Feb 09, 2024 at 04:56:36PM +, Francesco Turco wrote: > Hello. > > I have GNU texinfo 7.1 on a Gentoo Linux system. > > I can make texinfo reliably crash with the following simple steps: > 1. M-x set-variable > 2. Type "link-style" (without quotes) > 3. Type "foo" (without quotes) > >

Re: index sorting in texi2any in C issue with spaces

On Tue, Feb 13, 2024 at 05:37:03PM +0100, Patrice Dumas wrote: > On Mon, Feb 05, 2024 at 06:14:16PM +0000, Gavin Smith wrote: > > On Sun, Feb 04, 2024 at 10:27:00PM +0100, Patrice Dumas wrote: > > > removed at any time. Also calling it something else, like > > >

Re: not using OUTPUT_PERL_ENCODING to determine if _stream_encode should encode

On Sun, Feb 18, 2024 at 02:13:13PM +0100, Patrice Dumas wrote: > Hello, > > This is in the new encode once only stream code, so I ask here before > making a change, I could be missing something, Gavin you probably > will have comments/advices. > > I do not think that it is a good thing to set OUT

Re: Patch: stable sort for /usr/share/info/dir

On Sun, Feb 18, 2024 at 01:27:12PM +0100, Roland Clobus wrote: > Hello texinfo maintainers, > > While working on reproducible live images [1], I noticed that the sort order > in the file /usr/share/info/dir is unstable when nearly identical entries > are added. > > The order of the pairs 'diff',

Re: not using OUTPUT_PERL_ENCODING to determine if _stream_encode should encode

On Sun, Feb 18, 2024 at 10:57:22PM +0100, Patrice Dumas wrote: > On Sun, Feb 18, 2024 at 06:09:23PM +0000, Gavin Smith wrote: > > If this is ok, then "convert" could set $self->{'encoding_disabled'}. > > Should I do that part? I tried making the change

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

On Mon, Nov 06, 2023 at 07:52:40PM +0100, Andreas Schwab wrote: > On Nov 06 2023, Gavin Smith wrote: > > > $ readelf -d /usr/local/lib/texinfo/ConvertXS.so | grep RUNPATH > > 0x001d (RUNPATH)Library runpath: > > [/usr/local/lib/texinfo] >

Re: how to mix or avoid perl and gnulib headers and object files together?

On Fri, Feb 23, 2024 at 05:33:53PM +0100, Patrice Dumas wrote: > Hello, > > There are notes in C code warning against calling malloc or free and > functions potentially redefined by gnulib in files which include the > perl headers. It may be related to the discussion here: > > https://lists.gnu.

Intermittent test failure in t/03coverage_braces.t definfoenclose_texinfo_commands

I occasionally get test failures in the "perl -w t/03coverage_braces.t definfoenclose_texinfo_commands" test, but cannot usually repeat it reliably. I suspect some issue with memory corruption or issue with uninitialised memory, although I've not managed to get anything to show up with valgrind so

Re: Intermittent test failure in t/03coverage_braces.t definfoenclose_texinfo_commands

On Sun, Feb 25, 2024 at 04:47:46PM +, Gavin Smith wrote: > I occasionally get test failures in the > "perl -w t/03coverage_braces.t definfoenclose_texinfo_commands" test, > but cannot usually repeat it reliably. I suspect some issue with memory > corruption or issue wit

Re: Intermittent test failure in t/03coverage_braces.t definfoenclose_texinfo_commands

On Sun, Feb 25, 2024 at 07:01:22PM +, Gavin Smith wrote: > So it appears there is a problem with the counter not being reset properly > before the test runs, or sometime early on in the run. > > I'll try and do more investigation. It appears that there was no effort

Re: Intermittent test failure in t/03coverage_braces.t definfoenclose_texinfo_commands

On Sun, Feb 25, 2024 at 09:00:55PM +0100, Patrice Dumas wrote: > On Sun, Feb 25, 2024 at 07:43:42PM +0000, Gavin Smith wrote: > > It appears that there was no effort made to reset the counters at all. > > If a parser run finished with one of the counters active, it would > >

Re: how to mix or avoid perl and gnulib headers and object files together?

On Mon, Feb 26, 2024 at 01:15:47AM +0100, Patrice Dumas wrote: > On Fri, Feb 23, 2024 at 07:27:55PM +0000, Gavin Smith wrote: > > It is bad at any time. I'm not sure what situation you refer to by "link > > time". As far as I understand, the Perl headers redefine (o

Re: how to mix or avoid perl and gnulib headers and object files together?

On Tue, Feb 27, 2024 at 10:38:37PM +0100, Patrice Dumas wrote: > On Tue, Feb 27, 2024 at 08:10:31PM +0000, Gavin Smith wrote: > > On Mon, Feb 26, 2024 at 01:15:47AM +0100, Patrice Dumas wrote: > > > I did wrappers wrappers around functions to avoid mixing Perl and non-Perl >

Re: @itemize @asis is not well supported

On Mon, Mar 04, 2024 at 03:59:26PM +0100, Bruno Haible wrote: > @itemize @asis > seems to work in HTML and info mode only, not in TeX mode. > > > How to reproduce (with texinfo-7.1): Patrice covered most of it. It reproduces with any test file with "@itemize @asis" in it. > /tmp/gnulib/doc/gnu

Re: @itemize @asis is not well supported

On Tue, Mar 05, 2024 at 11:59:23AM +0100, Patrice Dumas wrote: > On Mon, Mar 04, 2024 at 09:16:44PM +0000, Gavin Smith wrote: > > \itemcontents expands to \asis and then TeX tries to take the } following > > as the argument to \asis, which is invalid. > > > > Basically

Re: @itemize @asis is not well supported

On Wed, Mar 06, 2024 at 03:05:06PM +0100, pertu...@free.fr wrote: > > I suggest > > > > ``` > > '@asis' needs braces here; say '@itemize @asis{}'. > > ``` > > I do not like much that option, because we do not have any idea why the > user ended up using '@itemize @asis'. Maybe with @asis, it will

Re: @itemize @asis is not well supported

On Tue, Mar 05, 2024 at 10:45:54PM +0100, Patrice Dumas wrote: > On Tue, Mar 05, 2024 at 07:44:33PM +0000, Gavin Smith wrote: > > I don't agree with changing the language to require braces. There is > > not a good reason to change it. Although writing "@itemize @bullet{}

Re: @itemize @asis is not well supported

On Thu, Mar 07, 2024 at 09:49:24AM +0100, Patrice Dumas wrote: > On Wed, Mar 06, 2024 at 09:54:18PM +0100, Bruno Haible wrote: > > Gavin Smith wrote: > > > it is not worth changing and making practically every use of > > > @itemize in a Texinfo manual being flagged

Re: @itemize @asis is not well supported

On Wed, Mar 13, 2024 at 03:42:19PM -0700, Raymond Toy wrote: > > I think both should be documented as being valid. I don't mind which one > > is presented as more normal. I have edited the node in the documentation > > slightly. > > > > It would be ok to change the example to show "@itemize @bull

Re: @itemize @asis is not well supported

On Thu, Mar 14, 2024 at 11:36:49PM +0100, Patrice Dumas wrote: > On Tue, Mar 12, 2024 at 06:39:46PM +0000, Gavin Smith wrote: > > I think both should be documented as being valid. I don't mind which one > > is presented as more normal. I have edited the node in the docume

Re: @itemize @asis is not well supported

On Thu, Mar 14, 2024 at 11:36:49PM +0100, Patrice Dumas wrote: > > I didn't really know what this part meant: > > > > Index entries and comments that are given before an @code{@@item} > > including the first, are automatically moved (internally) to after the > > @code{@@item}, so the o

Re: organization of the documentation of customization variables

On Sat, Mar 16, 2024 at 03:53:45PM +0100, Patrice Dumas wrote: > Hello, > > In a recent thread, on help-texinfo, Eli raised valid concerns on the > documentation of customization variables of texi2any, see for example: > https://lists.gnu.org/archive/html/help-texinfo/2024-03/msg00014.html Quotin

Re: proposal to remove AVOID_MENU_REDUNDANCY

On Sun, Mar 31, 2024 at 10:13:03PM +0200, Patrice Dumas wrote: > Hello, > > I propose to remove the HTML customization variable > AVOID_MENU_REDUNDANCY: > > If set, and the menu entry and menu description are the > same, then do not print the menu description; default false. > > It seems to me

Some links to external manuals not followable in Info output

If a cross-reference appears like @xref{,,, texi2any_api, GNU Texinfo @command{texi2any} Output Customization}. with no first argument, then this is output in Info like *Note (texi2any_api)::. - with no node argument following the manual. The Info browser (at least recent versions of it; I che

Re: Some links to external manuals not followable in Info output

On Wed, Apr 03, 2024 at 12:09:04PM +0200, Patrice Dumas wrote: > On Tue, Apr 02, 2024 at 09:56:40PM +0100, Gavin Smith wrote: > > If a cross-reference appears like > > > > @xref{,,, texi2any_api, GNU Texinfo @command{texi2any} Output > > Customization}. > > >

Re: renaming COMPLEX_FORMAT_IN_TABLE

On Sun, Mar 31, 2024 at 10:58:08PM +0200, Patrice Dumas wrote: > Hello, > > If the customization variable COMPLEX_FORMAT_IN_TABLE is set, > @indentedblock and indented fixed-width font @-commands, @example, > @display and @lisp are indented with a table (instead of using ). > > I think that the n

Re: removing NO_USE_SETFILENAME and USE_UP_NODE_FOR_ELEMENT_UP

On Wed, Apr 03, 2024 at 05:09:28PM +0200, Patrice Dumas wrote: > Hello, > > I would like to remove two customization options: > > NO_USE_SETFILENAME > If set, do not use @setfilename to set the document name; instead, base the > output document name only on the input file name. The default is fal

Re: renaming BODYTEXT as BODY_ELEMENT_ATTRIBUTES

On Wed, Apr 03, 2024 at 02:21:22PM +0200, Patrice Dumas wrote: > Hello, > > I propose to rename BODYTEXT as BODY_ELEMENT_ATTRIBUTES, I find BODYTEXT > not specific enough and confusing. It would also be more consistent > with the HTML_ROOT_ELEMENT_ATTRIBUTES customization variable name, which > i

Further reducing special case code for XS structuring

We previously discussed the interface of the XS modules and trying to improve their abstraction so that the same interface was used for both XS and non-XS code. (Emails from 2024-02-23 "Better abstraction of Texinfo::Document interface regardless of XS".) We made changes in this direction. There

Re: Further reducing special case code for XS structuring

On Wed, Apr 03, 2024 at 09:23:29PM +0100, Gavin Smith wrote: > We previously discussed the interface of the XS modules and trying to > improve their abstraction so that the same interface was used for both > XS and non-XS code. (Emails from 2024-02-23 "Better abstraction of >

Re: Further reducing special case code for XS structuring

On Wed, Apr 03, 2024 at 11:53:09PM +0200, Patrice Dumas wrote: > On Wed, Apr 03, 2024 at 09:23:28PM +0100, Gavin Smith wrote: > > This does appear to make texi2any work with TEXINFO_XS_STRUCTURE=0, although > > there are various test failures that I haven't investigated pro

Re: Further reducing special case code for XS structuring

On Wed, Apr 03, 2024 at 11:53:09PM +0200, Patrice Dumas wrote: > To avoid that, you could change the special call to $document->tree > with an argument, like $document->tree(1) to be $document->tree(), as > the argument, which is only taken in into account in XS is such that an > handler only is re

Re: Further reducing special case code for XS structuring

On Fri, Apr 05, 2024 at 12:20:19AM +0200, Patrice Dumas wrote: > I do not think that having the same interface for XS and pure Perl is > important. It could even make clearer what is going on in XS. What is > important is to have a code that is easy to understand as a whole in my > opinion. > >

Re: Further reducing special case code for XS structuring

On Fri, Apr 05, 2024 at 11:02:14PM +0200, Patrice Dumas wrote: > > I've committed a change to remove the $no_build parameter but not the > > $no_store parameter. > > It seems to me that the changes are no complete, to me the _get_parser_info > $no_build argument should be removed too, and the buil

Re: menu and sectioning consistency warning too strict?

On Wed, Apr 10, 2024 at 09:57:19PM +0200, Patrice Dumas wrote: > Hello, > > With CHECK_NORMAL_MENU_STRUCTURE set to 1, there is a warning by > texi2any: > > a.texi:10: warning: node `node after chap1' is next for `chap1' in menu but > not in sectioning > > for the following code: > > @node Top

Re: Suggestion: have a feature to enable synctex?

On Sat, May 04, 2024 at 03:56:14PM +0200, Patrice Dumas wrote: > On Sat, Apr 27, 2024 at 09:39:14PM +, user202...@protonmail.com wrote: > > Hello, > > > > I think a feature to support synctex in the compilation to PDF would be > > helpful, because it allows for quickly navigating between the

Re: avoiding access to NULL pointers coming from user customizations?

On Sat, May 04, 2024 at 07:28:01PM +0200, Patrice Dumas wrote: > Hello, > > With texi2any, customization variables can be set in Perl and used in C. > Customization variable strings undef in Perl become NULL char * pointers in > C, which is a natural and convenient representation. Some > customiz

Re: tiny main/utils.c fixes

On Wed, May 29, 2024 at 02:23:59PM -0400, Alfred M. Szmidt wrote: > Tiny patch; some older or newer compilers (I forgot which) will > complain if there is no compound statment after a label. Thank you! I am surprised it compiled before as a statement is supposed to follow a label - even a single

Re: 29 failed tests in the Texinfo 7.1 testsuite on Debian with IBM POWER9

On Sat, Jun 01, 2024 at 01:17:59AM -0400, Dennis Clarke via Bug reports for the GNU Texinfo documentation system wrote: > > I have no idea what this is such a terrible result : > > > > Testsuite summary for GNU Texinfo

Re: Multiline @cindex entries misrender in groff Texinfo manual

On Thu, May 16, 2024 at 10:41:44PM +0200, Patrice Dumas wrote: > On Thu, May 16, 2024 at 02:21:21PM -0500, G. Branden Robinson wrote: > > At 2024-05-16T12:55:51-0500, Dave Kemper wrote: > > > In a few places, the groff Texinfo manual uses a line-ending @ to > > > continue a @cindex entry. An examp

Re: texinfo 7.1: Segmentation fault when including texi file

On Wed, May 01, 2024 at 03:44:05PM +0200, Patrice Dumas wrote: > On Mon, Apr 29, 2024 at 08:58:12PM -0600, Christoph wrote: > > Hello, > > > > The build process fails during install target with a segmentation fault and > > the following message: > > texi2any (XS parser): bug: parent hv not already

updating ppport.h

I have attempted to follow the instructions in README-hacking to update tp/Texinfo/XS/ppport.h: Update ppport.h in tp/Texinfo/XS: perl -MDevel::PPPort -e'Devel::PPPort::WriteFile' However, this downgraded the version of the file. I tried to update the version of Devel::PPPort on my sys

ppport.h warnings - cv_name - html_get_button_specification_list

When I run ppport.h to get warnings, as stated in README-hacking, I get some warnings: *** WARNING: Uses sv_ref, which may not be portable below perl 5.23.5, even with 'ppport.h' This appears to be a false alarm due to local variables being called "sv_ref" which is also the name of a function ex

new functions in "make po-check"

There appear to be several new functions that have been added to po/Makevars but not recognised by "make po-check" (rule in top-level Makefile.am) to make a file contain translatable strings: message_list_document_error message_list_document_warn (others?) This means the output of "make po-check"

Re: 29 failed tests in the Texinfo 7.1 testsuite on Debian with IBM POWER9

On Sat, Jun 08, 2024 at 04:09:18AM -0400, Dennis Clarke wrote: > On 6/3/24 05:03, Patrice Dumas wrote: > > On Sun, Jun 02, 2024 at 02:31:11PM -0400, Dennis Clarke wrote: > > > The patch works ! > > > > Thanks for the report! > > > > @Gavin: this could go in 7.1 bugfix release, although with the u

Texinfo 7.1.0.90 pretest available

We have uploaded the pretest for the next minor, bug-fix release (7.1.1) of Texinfo, the GNU documentation format. https://alpha.gnu.org/gnu/texinfo/texinfo-7.1.0.90.tar.xz This bug-fix release is being made to make a release offically available with important problems fixed. Changes since versi

Re: texinfo-7.1.0.90 build report

On Sat, Jun 08, 2024 at 11:16:07AM -0600, Nelson H. F. Beebe wrote: > I have just completed build and validation attempts for > texinfo-7.1.0.90 on 52 systems, including several O/Ses (Linux, BSD, > and Solaris families), and CPUs (ARM64, PPC64LE, SPARC, x86, x86_64). > > Of those, 47 succeeded an

Re: Texinfo 7.1.0.90 pretest results [OpenBSD 7.5]

On Sun, Jun 09, 2024 at 03:58:08AM +0200, Bruno Haible wrote: > Summarizing the results from [2]: > > - On OpenBSD 7.5, there is a build failure: > Can't locate Texinfo/Commands.pm in @INC > For details, see the 'logs-openbsd' download from [2]. > [2] https://github.com/gnu-texinfo/c

Re: Texinfo 7.1.0.90 pretest results [OpenBSD 7.5]

On Sun, Jun 09, 2024 at 11:40:15AM +0100, Gavin Smith wrote: > It may be an issue with perl not having the right directory in its search > list (@INC). I will investigate more. I tried to fix one problem on the master branch (commit 2ae196b9807a, 2024-06-09). Hopefully the process of outp

Re: Texinfo 7.1.0.90 pretest results [OpenBSD 7.5]

On Mon, Jun 10, 2024 at 02:56:25PM +0200, Patrice Dumas wrote: > On Mon, Jun 10, 2024 at 01:27:58PM +0200, Bruno Haible wrote: > > Gavin Smith wrote: > > > I tried to fix one problem on the master branch (commit 2ae196b9807a, > > > 2024-06-09). > > > > Sin

Re: Texinfo master branch [OpenBSD]

On Mon, Jun 10, 2024 at 07:11:24PM +0200, Bruno Haible wrote: > > The time stamps are in the same order in my generated tarball. > With GNU make, there is no problem. The bug only occurs when OpenBSD 'make' > is used, in a VPATH build. The attached patch fixes the problem (I verified). > It is bas

Re: Texinfo 7.1.0.90 pretest results [OpenBSD 7.5]

On Mon, Jun 10, 2024 at 02:56:25PM +0200, Patrice Dumas wrote: > > 4) The Solaris 11 OmniOS build fails due to a test failure: > > > > FAIL: test_scripts/encoded_non_ascii_test_epub.sh > > > > Detailed log: > > --- > > >

Re: Texinfo master branch [mingw]

On Tue, Jun 11, 2024 at 11:54:16AM +0200, Bruno Haible wrote: > On mingw, I see 2 compilation errors: > > x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I../../info -I.. -I../.. > -I../../gnulib/lib -I../gnulib/lib -DLOCALEDIR=\"/usr/local/share/locale\" > -DINFODIR=\"/usr/local/share/info\" -DINF

Re: Texinfo master branch [Solaris 11 OmniOS]

On Thu, Jun 13, 2024 at 10:25:28PM +0200, Patrice Dumas wrote: > On Mon, Jun 10, 2024 at 07:11:53PM +0200, Bruno Haible wrote: > > It sounds like a bug in /bin/sh. And indeed, when I use bash to execute this > > script, no problem any more. It's not the first /bin/sh bug on this system > > that we

Re: declaring function pointers with explicit prototypes for the info reader

On Sun, Jun 16, 2024 at 05:37:48PM +0200, Patrice Dumas wrote: > On Sun, Jun 16, 2024 at 04:29:10PM +0200, Patrice Dumas wrote: > > Hello, > > > > In standalone info reader code in info/ most function pointers are > > declared as a generic function pointer VFunction *, defined in info.h as > > >

Re: Texinfo 7.1.0.90 pretest results [OpenBSD 7.5]

On Sun, Jun 09, 2024 at 08:06:53PM +0100, Gavin Smith wrote: > On Sun, Jun 09, 2024 at 11:40:15AM +0100, Gavin Smith wrote: > > It may be an issue with perl not having the right directory in its search > > list (@INC). I will investigate more. > > I tried to fix one problem

Re: Texinfo 7.1.0.90 pretest results [mingw]

On Sun, Jun 09, 2024 at 03:58:08AM +0200, Bruno Haible wrote: > Summarizing the results from [2]: > - On Cygwin and mingw, there are many test failures, some of which > look like CR-LF / LF mismatches. > > [2] https://github.com/gnu-texinfo/ci-check/actions/runs/9432971359 I was able to do

Re: add R-FAQ to htmlxref.cnf

On Fri, Jun 28, 2024 at 10:45:38AM +0200, Sebastian Meyer wrote: > The attached patch adds the R-FAQ > to the list of R manuals Thanks, I applied this. > (and also switches to the canonical form of the CRAN URL). Do you have any reference to s

Re: Patch to add use-package to htmlxref.cnf

On Fri, Jul 19, 2024 at 08:02:01PM +0200, Jacob Ilsø Christensen wrote: > The attached patch adds the Emacs use-package manuals to htmlxref.cnf. > > This will eventually (once manuals are regenerated with the updated > htmlxref.cnf) fix e.g. the broken link at the end of this page: > > https://ww

Re: add R-FAQ to htmlxref.cnf

On Mon, Jul 01, 2024 at 09:14:38AM +0200, Sebastian Meyer wrote: > > > (and also switches to the canonical form of the CRAN URL). > > > > Do you have any reference to say that using CRAN.R-project.org instead > > of cran.r-project.org is canonical? > > AFAIK, domain names are case insensitive, so

Re: Texinfo 7.1.0.90 pretest available

On Wed, Jul 03, 2024 at 08:23:01AM +, John Marshall wrote: > On 8 Jun 2024, at 23:02, Gavin Smith wrote: > > Please > > also feel to report if there are other problems that you feel should > > be fixed in this minor release. > > I think it would be worth applying

Re: Fix an error during "./configure; make dist"

On Mon, Jul 22, 2024 at 03:44:34AM +0200, Bruno Haible wrote: > Hi, > > According to the GNU Coding Standard > https://www.gnu.org/prep/standards/html_node/Standard-Targets.html > "The dist target should explicitly depend on all non-source files >that are in the distribution, to make sure th

Re: Math and the Emacs info viewer

On Wed, Jul 31, 2024 at 03:41:02PM +0200, Rahguzar wrote: > While this is true, I thought this might be the easier change. We just > need some markers. Even if I not handled, these markers wouldn't make > the presentation worse to a noticeable extent and Emacs being Emacs the > required changes can

Re: Fix an error during "./configure; make dist"

On Fri, Jul 26, 2024 at 12:03:55AM +0200, Patrice Dumas wrote: > On Tue, Jul 23, 2024 at 10:19:52PM +0100, Gavin Smith wrote: > > If it is just those lines, it may be an acceptable way to make "make dist" > > work without running "make" first, but I would want

Re: Fix an error during "./configure; make dist"

On Mon, Aug 05, 2024 at 07:03:08PM +0200, Bruno Haible wrote: > Patrice Dumas wrote: > Find attached two patches, to generate these two distributed files in the > source directory. Tested. Thanks for your continued testing and feedback. I've committed Patrice's fix and further fixes including one

Re: Fix an error during "./configure; make dist"

On Tue, Aug 06, 2024 at 06:59:28AM +0200, Bruno Haible wrote: > Hi Gavin, > > > In the other commit I made (a78e787fe3a) it was a simpler fix than the > > one you sent - hopefully it doesn't make a difference. (I want to keep > > it as simple and comprehensible as possible ... > > Well, there is

Re: fix an error message during configure

On Tue, Aug 06, 2024 at 09:45:25AM +0200, Bruno Haible wrote: > The fix to the problem is > 1) To apply the attached patch. Both the main configure.ac and > tp/Texinfo/XS/configure.ac use the same po/ directory. Since the version > of the gettext.m4 and related files must be in sync wit

Re: Fix an error during "./configure; make dist"

On Tue, Aug 06, 2024 at 03:58:37AM +0100, Gavin Smith wrote: > > Additionally, there is one more issue: > > > > 2) Texinfo/ModulePath.pm is no longer found in a particular situation > > (not sure whether this situation is supported). > > > > How to reproduc

master branch reverted

I've reverted the master branch up to commit 15f90529ee13 (2024-07-27) in an attempt to restore a stable working point. Recent attempts at fixing the build system (e.g. to run after "make maintainer-clean" was run) have only made things worse. "make distcheck" was not working due to an attempt t

Re: Fix an error during "./configure; make dist"

On Mon, Aug 05, 2024 at 05:15:21PM +0200, Patrice Dumas wrote: > On Mon, Aug 05, 2024 at 01:41:37PM +0200, Bruno Haible wrote: > > Hi Gavin, > > > > 2) "make distcheck" fails. (Reported by the weekly CI. It was fine a week > > ago.) > > Thanks for the report. > > Regarding the patch, the change

Re: fix an error message during configure

On Tue, Aug 06, 2024 at 10:20:28PM +0100, Gavin Smith wrote: > On Tue, Aug 06, 2024 at 09:45:25AM +0200, Bruno Haible wrote: > > The fix to the problem is > > 1) To apply the attached patch. Both the main configure.ac and > > tp/Texinfo/XS/configure.ac use the same po/

Re: Fix an error during "./configure; make dist"

On Thu, Aug 08, 2024 at 12:48:32PM +0200, Patrice Dumas wrote: > On Mon, Aug 05, 2024 at 07:03:08PM +0200, Bruno Haible wrote: > > Patrice Dumas wrote: > > > > This is not complete. > > > > 1) With this patch, the main texi2any_internals.texi still is generated in > > the > > build dir — which i

"make maintainer-clean" inconsistency

When I run "make maintainer-clean", there is a difference depending on whether it is an out-of-source build. In an in-source build, several files are deleted. After running "./configure ; make maintainer-clean", the output of "git status" includes: deleted:doc/html_default_commands_a

Re: fun with c23

On Thu, Aug 08, 2024 at 11:36:18PM -0600, Jeffrey Cliff wrote: > tl;dr c23 changes break compilation. 2 small patches > > [Firstly: apologize if this went to the wrong list - according to my > (terrible) email provider it didn't go out. Hopefully this is the > correct list] Yes, it's the correct

Re: fun with c23

On Fri, Aug 09, 2024 at 12:33:54PM +0200, Patrice Dumas wrote: > On Fri, Aug 09, 2024 at 10:23:53AM +0100, Gavin Smith wrote: > > On Thu, Aug 08, 2024 at 11:36:18PM -0600, Jeffrey Cliff wrote: > > > tl;dr c23 changes break compilation. 2 small patches > > > > >

Re: Fix an error during "./configure; make dist"

On Fri, Aug 09, 2024 at 05:31:32PM +0200, Patrice Dumas wrote: > Hello, > > The other cases raised by Bruno have been fixed, but this one still > fails: > > On Tue, Aug 06, 2024 at 06:59:28AM +0200, Bruno Haible wrote: > > Here's the recipe that currently still fails: > > > > $ ./autogen.sh > >

Re: Fix an error during "./configure; make dist"

On Sat, Aug 10, 2024 at 12:40:26AM +0200, Patrice Dumas wrote: > On Fri, Aug 09, 2024 at 11:08:02PM +0100, Gavin Smith wrote: > > With the attached patch, it cd's to srcdir before running pod2texi. > > This way pod2texi with --subdir works correctly. > > Looks like

Re: Fix an error during "./configure; make dist"

On Sat, Aug 10, 2024 at 04:23:29PM +0200, Patrice Dumas wrote: > On Sat, Aug 10, 2024 at 12:52:43PM +0200, Bruno Haible wrote: > > For the gnulib part, this is now fixed. Thanks for the report. > > Thanks! > > With Gavin change and some more I did on other generated files, we are > down to a diff

Re: fix an error message during configure

On Sat, Aug 10, 2024 at 06:03:01PM +0200, Patrice Dumas wrote: > Hello, > > The './autogen.sh' step in opencsw fails: > https://buildfarm.opencsw.org/buildbot/waterfall?category=texinfo > > It fails since commit > https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=d695e0fbef88a285884ccd1f16

Re: another build system suggestion

On Mon, Aug 12, 2024 at 12:47:06PM +0200, Bruno Haible wrote: > Texinfo already has 2 build-aux/ directories, but in the tp/Texinfo/XS/ > the automake-imported files are cluttering the main directory. How about > moving them to a build-aux/ directory there as well? > > Doing that consists of 3 ste

Re: fix an error message during configure

On Mon, Aug 12, 2024 at 12:29:10PM +0200, Bruno Haible wrote: > Yes, it fails in my CI as well: > > aclocal -I gnulib/m4 && autoconf && autoheader && automake > (cd tp/Texinfo/XS && libtoolize && aclocal -I gnulib/m4 && autoconf && > autoheader && automake) > libtoolize: putting auxiliary f

Re: fix an error message during configure

On Wed, Aug 14, 2024 at 02:15:14AM +0200, Bruno Haible wrote: > Gavin Smith wrote: > > > The first part serves the purpose of updating the same files also > > > in the build-aux/ directory, so that you don't risk distributing > > > outdated files for 6 years an

Re: [ANNOUNCE] GNU Texinfo 6.1 translated into Brazilian Portuguese

On Sun, Aug 11, 2024 at 03:34:48PM -0300, Jamenson Espindula wrote: > Hi all. > > I am very happy to announce the release of the GNU Texinfo (Version > 6.1) translated into Brazilian Portuguese. Congratulations at completing this project. Is this a release of all of the Texinfo software or just

Adding HTML navigation links [was Re: Suggestions for texi2any parsing]

On Thu, Jul 25, 2024 at 10:38:09PM +0200, Patrice Dumas wrote: > > == Adding a "Top" navigation entry > > > > For a web page I find it useful to be able to easily go to the > > homepage. I'm manually changing the HTML to add a "Top" navigation entry > > that points to the index page. I experimente

Re: Suggestions for texi2any parsing

On Thu, Jul 25, 2024 at 10:38:09PM +0200, Patrice Dumas wrote: > We have added a new command @nodedescription in the upcoming release > that contains the description that appears in @menus allowing to have an > automatic generation of menus with descriptions. For example: > > @node Copying Condit

Re: [ANNOUNCE] GNU Texinfo 6.1 translated into Brazilian Portuguese

On Wed, Aug 14, 2024 at 07:06:23PM -0300, Jamenson Espindula wrote: > Em qua., 14 de ago. de 2024 às 14:22, Gavin Smith > escreveu: > > > > Is this a release of all of the Texinfo software or just the documentation? > Just the documentation, specifically the texinfo.texi

Re: Can't build current HEAD with --enable-perl-xs on macOS

On Thu, Aug 15, 2024 at 03:59:23PM +0200, Dario Gjorgjevski wrote: > Building on macOS with --enable-perl-xs fails with: > > $ TEXINFO_DEV_SOURCE=1 top_srcdir="$(top_srcdir)" > top_builddir="$(top_builddir)" $(PERL) ../../tp/texi2any.pl -o > texi2any_internals.info texi2any_internals.texi >

Re: fix an error message during configure

On Wed, Aug 14, 2024 at 07:24:43PM +0200, Bruno Haible wrote: > Gavin Smith wrote: > > I'm not sure applying a patch such as this is the best way to upgrade > > these files. If these files came from Automake then it would make sense > > to update them from the Automake

BUG: format_line_message: error_location_info undef

On Thu, Aug 15, 2024 at 11:51:10PM +0200, Dario Gjorgjevski wrote: > > You say that TEXINFO_XS=debug does not show anything useful but it would > > still be helpful to see exactly how far it got successfully before failing. > > Here is the output: Is there something missing from this, as in a pre

Re: BUG: format_line_message: error_location_info undef

On Sat, Aug 17, 2024 at 09:08:09AM +0200, Patrice Dumas wrote: > On Fri, Aug 16, 2024 at 12:25:45AM +0100, Gavin Smith wrote: > > What makes the difference is the lack of the "-c > > INFO_SPECIAL_CHARS_WARNING=0" > > option. This produces thousands of lines of erro

Re: fix an error message during configure

On Fri, Aug 16, 2024 at 04:15:27PM +0200, Bruno Haible wrote: > Gavin Smith wrote: > > Also, if I delete build-aux/ar-lib nothing appears to regenerate it. > > Yes, I made the same experience. 'ar-lib' needs to be imported explicitly. > > > Perhaps it is

Re: Texinfo 7.1.0.90 pretest results [mingw]

On Mon, Jun 17, 2024 at 08:59:54PM +0100, Gavin Smith wrote: > On Sun, Jun 09, 2024 at 03:58:08AM +0200, Bruno Haible wrote: > > Summarizing the results from [2]: > > > - On Cygwin and mingw, there are many test failures, some of which > > look like CR-LF / LF mismat

Re: Texinfo 7.1.0.90 pretest results [mingw]

On Tue, Aug 20, 2024 at 12:29:39AM +0200, Bruno Haible wrote: > Hi Gavin, > > > If someone could confirm that this works for mingw where > > --strip-trailing-cr is needed for diff > > The current texinfo from git builds fine, with all tests passed!, > on mingw 5.0 in a Cygwin environment. > > Ve

Re: EPUB 3.3 spec conformity issues

On Wed, Aug 21, 2024 at 05:59:03PM +0200, Patrice Dumas wrote: > On Tue, Aug 20, 2024 at 09:23:57AM +0100, Daniel Cerqueira wrote: > > > > The dcterms:modified meta element is MANDATORY in order to create a > > valid EPUB 3.3 file. It is missing in the current Texinfo EPUB file > > creation. Here i

Re: EPUB 3.3 spec conformity issues

On Tue, Aug 20, 2024 at 11:13:59PM +0100, Daniel Cerqueira wrote: > Thinking more deeply, I have changed the HTML.pm patch. > > The border property of the table element, if set to "1" (instead of ""), > probably is best for HTML generation, and still produces a valid EPUB > 3.3. > This can't go

Re: EPUB 3.3 spec conformity issues

On Wed, Aug 21, 2024 at 06:34:34PM +0100, Daniel Cerqueira wrote: > From https://www.w3.org/TR/epub-33/#sec-conformance-checking > > ``` > Due to the complexity of this specification and number of technologies > used in EPUB publications, EPUB creators are advised to use an EPUB > conformance chec

Re: References in section titles (invalid HTML generated)

On Thu, Aug 22, 2024 at 03:42:20PM +0200, Rudolf Adamkovič wrote: > Alternatively, if references in titles cannot possibly be supported, > then Texinfo should warn about them, instead of generating invalid HTML. References inside section headings was discussed before and it seemed that we were goi

<    1   2   3   4   5   6   7   8   9   10   >