Re: dependency on libperl?

On Mon, Jul 21, 2025 at 10:29:24PM +0100, Gavin Smith wrote: > > Is the mandatory dependency on libperl intended? > > > > Bruno > > It shouldn't depend on libperl. As far as I understand, libperl can come > in two ways (Patrice could confirm this). > > The first is when building the C implement

Re: compilation error on NetBSD

On Mon, Jul 21, 2025 at 11:02:17PM +0200, Bruno Haible via Bug reports for the GNU Texinfo documentation system wrote: > The CI reports a compilation error on NetBSD 10.0: > > gcc -DHAVE_CONFIG_H -I. -I../../info -I.. -I../.. > -I../../gnulib/lib

Re: dependency on libperl?

On Mon, Jul 21, 2025 at 11:05:24PM +0200, Bruno Haible via Bug reports for the GNU Texinfo documentation system wrote: > The CI reports a link error on Ubuntu (both when compiling natively and > when cross-compiling for RISCV), that was not present last week: > > /bin/bash ../../libtool --tag=CC

Re: "make distcheck" failure

Gavin Smith wrote: > Thanks for the report and apologies for the inconvenience. I have fixed > in commit 9ce27563568c (today's date). OK, I'm starting a new CI run (because you certainly want to know if there happen to be other regressions). Bruno

Re: "make distcheck" failure

On Mon, Jul 21, 2025 at 09:04:09PM +0200, Bruno Haible via Bug reports for the GNU Texinfo documentation system wrote: > Hi, > > The CI reports today that, unlike a week ago, "make distcheck" fails: > > (cd info && make top_distdir=../texinfo-7.2.20250721dev > distdir=../texinfo-7.2.20250721d

Re: [PATCH v1 1/1] Short Sample: show how to avoid warning: node `[...]' unreferenced.

On Sat, 19 Jul 2025 14:25:12 +0100 Gavin Smith wrote: > The @menu block you have added is unnecessary in newer versions of > Texinfo and I don't understand what you hope to achieve by adding in > back in. OK, so it's already fixed, thanks a lot, and sorry for the noise. Denis. pgpi_SZD_AUPQ.pg

Re: [PATCH v1 1/1] Short Sample: show how to avoid warning: node `[...]' unreferenced.

On Sat, Jul 19, 2025 at 02:20:36AM +0200, Denis 'GNUtoo' Carikli wrote: > While the current Short Sample work fine, if we remove the second > section and run run the following command: >makeinfo -D "VERSION 0.1" -D "UPDATED now" shortsample.texi' > we end up with the following warning: > sh

Re: Unable to build Texinfo from git ("SWIG not found")

On Fri, Jul 18, 2025 at 06:46:35PM +0200, Andreas Schwab wrote: > > -- Macro: AC_ARG_WITH (PACKAGE, HELP-STRING, [ACTION-IF-GIVEN], > > [ACTION-IF-NOT-GIVEN]) > > > > The option now looks like it was given, so the third argument to > > AC_ARG_WITH, [ with_swig='yes' ], runs, leading to

Re: Highlight syntax with source-highlight produces error with split html output

On Fri, Jul 18, 2025 at 10:27:34AM -0700, Raymond Toy wrote: > Well, dang. I don't get this error anymore either. I didn't change anything. > > Oh, wait. If I remove src-hl_html/, I get the error. But if I run it again, > I don't. And the files are all there as you show. You figured it out. I'm

Re: Highlight syntax with source-highlight produces error with split html output

On 7/18/25 9:47 AM, Gavin Smith wrote: On Fri, Jul 18, 2025 at 08:43:21AM -0700, Raymond Toy wrote: |@include src-hl.c | I changed it to |#include src-hl.c | Now I get the message: |texi2any: warning: highlight_syntax.pm: could not open src-hl_html/src-hl_highlight_C_input.C: No such file o

Re: Highlight syntax with source-highlight produces error with split html output

On Fri, Jul 18, 2025 at 08:43:21AM -0700, Raymond Toy wrote: > |@include src-hl.c | > > I changed it to > > |#include src-hl.c | > > Now I get the message: > > |texi2any: warning: highlight_syntax.pm: could not open > src-hl_html/src-hl_highlight_C_input.C: No such file or directory | > > It a

Re: Unable to build Texinfo from git ("SWIG not found")

On Jul 18 2025, Gavin Smith wrote: > On Thu, Jul 17, 2025 at 02:28:20AM +0100, Gavin Smith wrote: >> The responsible code is in tta/configure.ac: >> >> >> - >> # SWIG interfaces >> >> # FIXME if enable_xs=yes and embedded_p

Re: Highlight syntax with source-highlight produces error with split html output

On 7/18/25 8:56 AM, Gavin Smith wrote: On Fri, Jul 18, 2025 at 08:43:21AM -0700, Raymond Toy wrote: Huh, this is weird. Perhaps I messed up building texinfo 7.2 from sources a while back? Anyway, with your test, I ran it. I get a message that it can't include src-hl.c. That seems to come from

Re: Highlight syntax with source-highlight produces error with split html output

On Fri, Jul 18, 2025 at 08:43:21AM -0700, Raymond Toy wrote: > Huh, this is weird. Perhaps I messed up building texinfo 7.2 from sources a > while back? > > Anyway, with your test, I ran it. I get a message that it can't include > src-hl.c. That seems to come from the line > > |@include src-hl.c

Re: Highlight syntax with source-highlight produces error with split html output

On 7/18/25 7:04 AM, Gavin Smith wrote: On Wed, Jul 16, 2025 at 02:27:25PM -0700, Raymond Toy wrote: I'm experimenting with HIGHLIGHT_SYNTAX=source-highligit. It works fine with --no-split and produces pretty nice highlighting. However, when I don't use --no-split, I get an error. An example er

Re: Unable to build Texinfo from git ("SWIG not found")

On Thu, Jul 17, 2025 at 02:28:20AM +0100, Gavin Smith wrote: > The responsible code is in tta/configure.ac: > > > - > # SWIG interfaces > > # FIXME if enable_xs=yes and embedded_perl=no, the interface will need > # to build

Re: Highlight syntax with source-highlight produces error with split html output

On Wed, Jul 16, 2025 at 02:27:25PM -0700, Raymond Toy wrote: > I'm experimenting with HIGHLIGHT_SYNTAX=source-highligit. It works fine with > --no-split and produces pretty nice highlighting. > > However, when I don't use --no-split, I get an error. An example error > message: > > |makeinfo: warn

Re: Texinfo 7.2 pdf output for @example lisp

On 7/16/25 2:38 PM, Gavin Smith wrote: On Wed, Jul 16, 2025 at 02:13:43PM -0700, Raymond Toy wrote: If I have a texinfo file that has |@example lisp (defun foo (x) (+ x x)) @end example | (The line breaks are not present in the plaintext version of your email). Oops. Sorry! I used the versi

Re: Texinfo 7.2 pdf output for @example lisp

On Wed, Jul 16, 2025 at 02:13:43PM -0700, Raymond Toy wrote: > If I have a texinfo file that has > > |@example lisp (defun foo (x) (+ x x)) @end example | (The line breaks are not present in the plaintext version of your email). > > and do |texinfo --pdf|, (with texinfo 7.2), the pdf output lo

Re: Info hook script for file not found?

On Wed, Jul 16, 2025 at 04:19:53PM +0200, Patrice Dumas wrote: > On Wed, Jul 16, 2025 at 12:57:03AM +0100, Gavin Smith wrote: > > This feature still needs work: > > > > * At what point do we run the hook - before checking for man pages, > > or after? E.g. if "tar.info" is not installed but the ta

Re: Info hook script for file not found?

On Wed, Jul 16, 2025 at 12:57:03AM +0100, Gavin Smith wrote: > This feature still needs work: > > * At what point do we run the hook - before checking for man pages, > or after? E.g. if "tar.info" is not installed but the tar man page > is installed, should "info tar" run the hook, or display the

Re: Info hook script for file not found?

On Sun, Feb 23, 2025 at 03:51:47PM +, Gavin Smith wrote: > I've commited code to use a hook program under > "XDG_CONFIG_DIRS/texinfo/info-hooks/manual-not-found", where XDG_CONFIG_DIRS > could be e.g. $HOME/.config or /etc/xdg. Previous discussion: https://lists.gnu.org/archive/html/bug-texin

Re: Start on replacement for titlepage in texinfo.tex

On Tue, Jul 15, 2025 at 02:27:05PM +0300, Eli Zaretskii wrote: > > It would be good in my opinion to get rid of the @vskip line as it > > looks ugly and confusing and probably turns people off. > > I think this calls for some research: how many manuals do NOT use the > standard @vskip line, and if

Re: Start on replacement for titlepage in texinfo.tex

> From: Gavin Smith > Date: Mon, 14 Jul 2025 21:13:20 +0100 > > On Mon, Jun 30, 2025 at 11:30:30PM +0100, Gavin Smith wrote: > > So just using @maketitle to produce the copyright page too is > > a real possibility. > > So I've been seeing what I can implement in texinfo.tex as a prototype > for

Re: Start on replacement for titlepage in texinfo.tex

> I've also implemented a "@publication" command in texinfo.tex, that > should contain information about the publisher and any other details > specific to the act of publication. [...] This looks nice, thank you. Werner

Re: Start on replacement for titlepage in texinfo.tex

On Mon, Jul 14, 2025 at 09:13:36PM +0100, Gavin Smith wrote: > On Mon, Jun 30, 2025 at 11:30:30PM +0100, Gavin Smith wrote: > > So just using @maketitle to produce the copyright page too is > > a real possibility. > > So I've been seeing what I can implement in texinfo.tex as a prototype > for thi

Re: epsf.tex: New file

(Cc-ing bug-texinfo. Oddly, Gavin and I were just talking about epsf.tex. Bruno's original message: https://lists.gnu.org/archive/html/bug-gnulib/2025-07/msg00083.html) So, the problem is not limited to Bison. It occurs because epsf.tex is a dependency of (in fact, the only dependency of)

Re: Texinfo::Common::debug_print_tree doesn't work well with Texinfo::TreeElement

On Fri, Jul 11, 2025 at 01:15:50PM +0100, Gavin Smith wrote: > > There is the $Data::Dumper::Toaster function in Data::Dumper that could > > be used to do something for each blessed object, maybe copy it without > > blessing? > > It is $Data::Dumper::Freezer that does something before it is > dump

Re: Could texinfo.tex skip re-reading defaults from txi-en.tex ?

On Fri, Jul 11, 2025 at 06:35:04PM +0100, Gavin Smith wrote: > On Fri, Jul 11, 2025 at 07:14:13PM +0200, Sebastian Meyer wrote: > > Would it make sense for texinfo.tex to skip over @documentlanguage en when > > no other language has been set before? > > It seems like it is a special case for not m

Re: Could texinfo.tex skip re-reading defaults from txi-en.tex ?

On Fri, Jul 11, 2025 at 07:14:13PM +0200, Sebastian Meyer wrote: > Now that CTAN no longer contains the translation files (following a recent > thread on this list, > ), the > texinfo bundle from CTAN is no longer sufficient to p

Could texinfo.tex skip re-reading defaults from txi-en.tex ?

Now that CTAN no longer contains the translation files (following a recent thread on this list, ), the texinfo bundle from CTAN is no longer sufficient to process the following minimal Texinfo document \input texinfo

Re: Texinfo::Common::debug_print_tree doesn't work well with Texinfo::TreeElement

On Fri, Jul 11, 2025 at 11:26:19AM +0200, Patrice Dumas wrote: > On Fri, Jul 11, 2025 at 12:45:05AM +0100, Gavin Smith wrote: > > As Texinfo tree elements are now blessed into the Texinfo::TreeElement > > class, this class is output by Data::Dumper when used by > > Texinfo::Common::debug_print_tree

Re: Texinfo::Common::debug_print_tree doesn't work well with Texinfo::TreeElement

On Fri, Jul 11, 2025 at 12:45:05AM +0100, Gavin Smith wrote: > As Texinfo tree elements are now blessed into the Texinfo::TreeElement > class, this class is output by Data::Dumper when used by > Texinfo::Common::debug_print_tree. I use this fairly often when developing > and/or debugging. Sample

Re: why 'verbatim' output for menu comments in HTML?

> I edited the documentation slightly. It should be covered by the > sentence, "Menu comment lines and any empty lines are kept in the > output." Thanks, this looks good. Werner

Re: why 'verbatim' output for menu comments in HTML?

On Wed, Jul 09, 2025 at 07:23:53AM +, Werner LEMBERG wrote: > > >> OK, so please document this. Looking at section `Writing a menu` > >> in the Texinfo info file (of current git) I don't see anything > >> about HTML output of `@menu` blocks and how it is formatted (and > >> the description of

Re: how to get HTML navigation panel in footer with `-c FORMAT_MENU=menu`

>> Ouch! I simply searched for the string 'footer' in the Texinfo >> info pages and I got no hit. I now see that the description of >> `WORDS_IN_PAGE` is in the 'Customization of Navigation and Headers' >> section (as it should be), which I missed. > > You could also have checked the indices w

Re: how to get HTML navigation panel in footer with `-c FORMAT_MENU=menu`

On Wed, Jul 09, 2025 at 05:04:34AM +, Werner LEMBERG wrote: > Ouch! I simply searched for the string 'footer' in the Texinfo info > pages and I got no hit. I now see that the description of > `WORDS_IN_PAGE` is in the 'Customization of Navigation and Headers' > section (as it should be), whic

Re: ugly page break in ToC

>> Both are OK to me. However, what I have a problem with are cases >> where too much empty vertical space remains, which could be easily >> filled with a chapter entry and four lower-level entries, say. > > I've made a change changing this dimension down to 30pt. Thanks. > I know you said yo

Re: why 'verbatim' output for menu comments in HTML?

>> OK, so please document this. Looking at section `Writing a menu` >> in the Texinfo info file (of current git) I don't see anything >> about HTML output of `@menu` blocks and how it is formatted (and >> the description of `FORMAT_MENU` doesn't mention this either). > > In general, we do not d

Re: why 'verbatim' output for menu comments in HTML?

On Wed, Jul 09, 2025 at 06:18:15AM +, Werner LEMBERG wrote: > > Hello Patrice and Gavin, > > > thanks for your answers. > > >> Why ``? I consider this surprising since the item description > >> of a menu entry (i.e., the third part of an entry) is not output > >> with ``. > > > > The idea

Re: script for updating CSS entities

>> Maybe you can provide a list of the most important CSS changes, or >> maybe add a section that describes how to do the transition to >> Texinfo 7.0 and newer? > > Here is what is in tta/TODO (which is more notes than TODO). We > have not formally described that in the Texinfo manual because we

Re: script for updating CSS entities

On Wed, Jul 09, 2025 at 06:36:08AM +, Werner LEMBERG wrote: > Maybe you can provide a list of the most important CSS changes, or > maybe add a section that describes how to do the transition to Texinfo > 7.0 and newer? Here is what is in tta/TODO (which is more notes than TODO). We have not f

Re: script for updating CSS entities

>> Comparing the HTML of version 6.8 with version 7.2, I see that many >> classes got new names. This means that we essentially have to >> rewrite our custom CSS file, which is not fun. >> >> What about providing a script >> >> ``` >> texinfo-css-update --from 6.8 --to 7.2 < infile > outfile >> ``

Re: why 'verbatim' output for menu comments in HTML?

Hello Patrice and Gavin, thanks for your answers. >> Why ``? I consider this surprising since the item description >> of a menu entry (i.e., the third part of an entry) is not output >> with ``. > > The idea was that the users may have wanted to have the end lines > and spaces to be signific

Re: how to get HTML navigation panel in footer with `-c FORMAT_MENU=menu`

>> What must I do to always get a navigation panel in the footer >> (i.e., `NODE_FOOTER_BUTTONS`)? > > texi2any --html -c FORMAT_MENU=menu -c WORDS_IN_PAGE=0 test.texi > > The setting of FORMAT_MENU is immaterial. Thanks! > This question has been asked so many times before that I wonder if >

Re: script for updating CSS entities

On Tue, Jul 08, 2025 at 10:53:39PM +0100, Gavin Smith wrote: > and the one I found was this: > > https://lilypond.org/doc/v2.25/Documentation/css/lilypond-manuals.css > > If that is the only CSS file, then it seems plausible that we could work > together on what would have to be updated. I'm afr

Re: script for updating CSS entities

On Tue, Jul 08, 2025 at 12:19:58PM +, Werner LEMBERG wrote: > > Comparing the HTML of version 6.8 with version 7.2, I see that many > classes got new names. This means that we essentially have to rewrite > our custom CSS file, which is not fun. > > What about providing a script > > ``` > te

Re: script for updating CSS entities

On Tue, Jul 08, 2025 at 12:19:58PM +, Werner LEMBERG wrote: > > Comparing the HTML of version 6.8 with version 7.2, I see that many > classes got new names. This means that we essentially have to rewrite > our custom CSS file, which is not fun. > > What about providing a script > > ``` > te

Re: how to get HTML navigation panel in footer with `-c FORMAT_MENU=menu`

On Tue, Jul 08, 2025 at 07:42:13PM +, Werner LEMBERG wrote: > > [texi2any 6.8, 7.2] > > > texi2any --html -c FORMAT_MENU=menu menu.texinfo > ``` > > There is only a header but no footer navigation panel. > > What must I do to always get a navigation panel in the footer (i.e., > `NODE_FOOT

Re: why 'verbatim' output for menu comments in HTML?

On Tue, Jul 08, 2025 at 12:07:11PM +, Werner LEMBERG wrote: > > [texi2any 7.2] > > > texi2any --html -c FORMAT_MENU=menu menu.texinfo > ``` > > the menu comment in output file `index.html` gets formatted like this: > > ``` > > > > XXX yyy ZZZ > > > > ``` > > Why ``? I consider thi

Re: why 'verbatim' output for menu comments in HTML?

On Tue, Jul 08, 2025 at 12:07:11PM +, Werner LEMBERG wrote: > > [texi2any 7.2] > > > Consider the following example file `menu.texinfo`. > > ``` > \input texinfo > > @node Top > @top Top > > @menu > * Foo:: Foo foo foo. > > > XXX @var{yyy} ZZZ > > > * Bar:: Bar bar bar. > @end menu >

Re: how to get HTML navigation panel in footer with `-c FORMAT_MENU=menu`

On Tue, Jul 08, 2025 at 07:42:13PM +, Werner LEMBERG wrote: > There is both a header and a footer navigation panel. However, the > files `Foo.html` and `Bar.html` look like the following: > > ``` > Previous: Foo, Up: Top > --- > > ... > > ``` > > There is only a

Re: ugly page break in ToC

On Mon, Jul 07, 2025 at 06:08:37PM +, Werner LEMBERG wrote: > > I am not really sure which is better. There is more in chapter 17 > > and one argument is that it is better to start a new page for > > chapter 17's contents listing. > > Both are OK to me. However, what I have a problem with ar

Re: ugly page break in ToC

>> Thanks, this helps: for my version of the LilyPond Notation >> Reference a value of 10pt works just fine. Before that I tried >> 20pt, however, I got a different but equally bad gap as reported >> originally. This makes me wonder whether we are we really turning >> the right screw... > > I tr

Re: ugly page break in ToC

>> While playing around with adding parts to LilyPond's Notation >> Reference, I got the attached layout in the ToC. As can be seen, >> there is a vertical gap corresponding to approx. 8 lines(!) at the >> bottom of page vi; I've never noticed such a large gap before in any >> Texinfo document. [

Re: better PDF formatting of `@part` in ToC

>> I played around a bit more, and I think it looks good if the >> vertical space right before the part entry gets increased a bit, >> see attached image. > > I think it will be safest to keep the same size for the text, > and just to use increased spacing before the part line to separate > it v

Re: wrong to use Index match in Info reader for the presence of index?

On Sun, Jun 29, 2025 at 11:55:11PM +0200, Patrice Dumas wrote: > On Sat, Jun 28, 2025 at 07:54:36PM +0100, Gavin Smith wrote: > > > I checked that a tag that is not 'Node:' or 'Ref:' has the Info reader > > > (but not the Emacs Info reader) stop going through tags immediatly. > > > This means that

Re: ugly page break in ToC

On Mon, Jul 07, 2025 at 06:10:52AM +, Werner LEMBERG wrote: > > [texinfo.tex 2025-03-22.08] > [luatex Version 1.22.0 (TeX Live 2025), Development id: 7673] > > > While playing around with adding parts to LilyPond's Notation > Reference, I got the attached layout in the ToC. As can be seen,

Re: better PDF formatting of `@part` in ToC

> Since `@part` is outside of the sectioning hierarchy I suggest to > not indent it at all, see the second attached image; doing so has > the additional bonus that it sticks out more prominently – right > now, because it uses the same font and size as ToC entries for > `@chapter`, it can be easily

Re: ugly page break in ToC

> While playing around with adding parts to LilyPond's Notation > Reference, I got the attached layout in the ToC. As can be seen, > there is a vertical gap corresponding to approx. 8 lines(!) at the > bottom of page vi; I've never noticed such a large gap before in any > Texinfo document. > > I

Re: New structure warnings and deeply nested nodes in libc manual

On Sat, Jul 05, 2025 at 08:30:06PM +0100, Gavin Smith wrote: > I used a loop like this: > > # Find the first subordinate section, which should appear first > # in the menu. > my $first_child = $section_children->[0]; > while (!defined($first_child->{'associated_node'}) >

Re: New structure warnings and deeply nested nodes in libc manual

On Sat, Jul 05, 2025 at 10:29:00AM +0200, Patrice Dumas wrote: > On Sat, Jul 05, 2025 at 01:06:29AM +0100, Gavin Smith wrote: > > On Fri, Jul 04, 2025 at 10:18:05PM +0100, Gavin Smith wrote: > > > All these nodes (in the Sphinx output) have explicit pointers on the > > > node lines, just like the a

Re: New structure warnings and deeply nested nodes in libc manual

On Sat, Jul 05, 2025 at 01:06:29AM +0100, Gavin Smith wrote: > On Fri, Jul 04, 2025 at 10:18:05PM +0100, Gavin Smith wrote: > > All these nodes (in the Sphinx output) have explicit pointers on the > > node lines, just like the affected part of the libc manual. > > > > So I expect we will have to t

Re: New structure warnings and deeply nested nodes in libc manual

On Fri, Jul 04, 2025 at 10:18:05PM +0100, Gavin Smith wrote: > All these nodes (in the Sphinx output) have explicit pointers on the > node lines, just like the affected part of the libc manual. > > So I expect we will have to take some account of node pointers > when generating these warnings. (W

Re: New structure warnings and deeply nested nodes in libc manual

On Mon, Jun 23, 2025 at 12:20:05AM +0200, Patrice Dumas wrote: > > > I do not really understand the comment explaining why Getopt and argp > > > start at the @section level, I do not get what "enough room for their > > > internal hierarchy" means, so it is not clear to me why the Glibc people > > >

Re: replacement for titlepage and more metadata commands

On Wed, Jul 02, 2025 at 11:23:14PM +0200, Patrice Dumas wrote: > > I've been learning about features in "KOMA-Script" (a LaTeX system) > > that allow for the creation of copyright pages: > > > > https://tex.stackexchange.com/questions/12570/how-to-add-a-copyright-page-to-the-report-class > > https

Re: replacement for titlepage and more metadata commands

On Mon, Jun 30, 2025 at 11:30:29PM +0100, Gavin Smith wrote: > On Sun, Jun 29, 2025 at 06:53:20PM +0200, Patrice Dumas wrote: > > > The user uses @maketitle to produce the title page, and the second page > > > is created by the contents of the @copyrightpage block. > > > > > > We could also possib

Re: replacement for titlepage and more metadata commands

On Sun, Jun 29, 2025 at 06:53:20PM +0200, Patrice Dumas wrote: > > The user uses @maketitle to produce the title page, and the second page > > is created by the contents of the @copyrightpage block. > > > > We could also possibly provide a @makecopyrightpage command > > for a default copyright pag

Re: wrong to use Index match in Info reader for the presence of index?

On Mon, Jun 30, 2025 at 04:51:24PM +0100, Gavin Smith wrote: > I am not a fan of the idea of adding a Local Variable for > this. Space is limited in that section. From Info.pm: > > # Note: Info readers expect the Local Variables section to be > # under 1000 bytes in length so not many va

Re: wrong to use Index match in Info reader for the presence of index?

On Mon, Jun 30, 2025 at 04:04:12PM +0300, Eli Zaretskii wrote: > > Date: Mon, 30 Jun 2025 14:48:40 +0200 > > From: pertu...@free.fr > > Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org > > > > On Mon, Jun 30, 2025 at 02:47:01PM +0300, Eli Zaretskii wrote: > > > > Date: Sun, 29 Jun 2025 18:59:22 +

Re: wrong to use Index match in Info reader for the presence of index?

> Date: Mon, 30 Jun 2025 14:48:40 +0200 > From: pertu...@free.fr > Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org > > On Mon, Jun 30, 2025 at 02:47:01PM +0300, Eli Zaretskii wrote: > > > Date: Sun, 29 Jun 2025 18:59:22 +0200 > > > From: pertu...@free.fr > > > > > > What about adding a 'Local V

Re: wrong to use Index match in Info reader for the presence of index?

On Mon, Jun 30, 2025 at 02:47:01PM +0300, Eli Zaretskii wrote: > > Date: Sun, 29 Jun 2025 18:59:22 +0200 > > From: pertu...@free.fr > > > > What about adding a 'Local Variables' with the name of the first node > > with indices with makeinfo and using that instead of "Index" in nodes > > names to d

Re: wrong to use Index match in Info reader for the presence of index?

> Date: Sun, 29 Jun 2025 18:59:22 +0200 > From: pertu...@free.fr > > What about adding a 'Local Variables' with the name of the first node > with indices with makeinfo and using that instead of "Index" in nodes > names to determine the first node with indices as I proposed? Is it a valid assumpti

Re: Test failures with Perl 5.42

Patrice Dumas writes: > On Mon, Jun 30, 2025 at 06:42:56AM +0100, Sam James wrote: >> Hi, >> >> Perl 5.42 will be released shortly. Testing texinfo-7.2 (but also trunk) >> with perl-5.42.0_rc2, I see many test failures: > > This was already reported and there were some fixes (for trunk): > > htt

Re: Test failures with Perl 5.42

On Mon, Jun 30, 2025 at 06:42:56AM +0100, Sam James wrote: > Hi, > > Perl 5.42 will be released shortly. Testing texinfo-7.2 (but also trunk) > with perl-5.42.0_rc2, I see many test failures: This was already reported and there were some fixes (for trunk): https://lists.gnu.org/archive/html/bug-

Re: replacement for titlepage and more metadata commands

On Sun, Jun 29, 2025 at 09:12:41PM +0100, Gavin Smith wrote: > On Sun, Jun 29, 2025 at 06:53:20PM +0200, Patrice Dumas wrote: > > > title verso page for TeX output (and possibly LaTeX output with texi2any). > > > I don't think it's advisable to try and make it automatic. Sometimes > > > users > >

Re: wrong to use Index match in Info reader for the presence of index?

On Sat, Jun 28, 2025 at 07:54:36PM +0100, Gavin Smith wrote: > > I checked that a tag that is not 'Node:' or 'Ref:' has the Info reader > > (but not the Emacs Info reader) stop going through tags immediatly. > > This means that a new tag would break the Info readers from previous > > releases. Ind

Re: replacement for titlepage and more metadata commands

On Sun, Jun 29, 2025 at 06:53:20PM +0200, Patrice Dumas wrote: > On Sun, Jun 29, 2025 at 01:31:31AM +0100, Gavin Smith wrote: > > > > In the default case, when using @documentinfo, the copying text would > > > > be output > > > > on the verso of the title page in PDF output. No separate command

Re: wrong to use Index match in Info reader for the presence of index?

On Sat, Jun 28, 2025 at 08:53:21PM +0100, Gavin Smith wrote: > On Sat, Jun 28, 2025 at 10:23:59PM +0300, Eli Zaretskii wrote: > > > From: Gavin Smith > > > Date: Sat, 28 Jun 2025 19:54:36 +0100 > > > > > > I also don't think it is a huge restriction to have "Index" in the > > > node name. Non-En

Re: replacement for titlepage and more metadata commands

On Sun, Jun 29, 2025 at 01:31:31AM +0100, Gavin Smith wrote: > > > In the default case, when using @documentinfo, the copying text would be > > > output > > > on the verso of the title page in PDF output. No separate command would > > > be > > > necessary. > > > > It is necessary if the user wa

Re: New structure warnings and deeply nested nodes in libc manual

On Sun, Jun 29, 2025 at 02:42:08PM +0300, Eli Zaretskii wrote: > > It's because there are three menu entries for the same node. The > > first menu entry is expected because that node is subordinate in > > the sectioning structure (a @subsection underneath a @section), > > but the other two are une

Re: New structure warnings and deeply nested nodes in libc manual

> From: Gavin Smith > Date: Sun, 29 Jun 2025 12:06:46 +0100 > Cc: pertu...@free.fr, bug-texinfo@gnu.org > > On Sun, Jun 29, 2025 at 07:50:47AM +0300, Eli Zaretskii wrote: > > > From: Gavin Smith > > > Date: Sat, 28 Jun 2025 21:45:03 +0100 > > > > > > And now I have warnings with this manual (pa

Re: New structure warnings and deeply nested nodes in libc manual

On Sun, Jun 29, 2025 at 07:44:09AM +0300, Eli Zaretskii wrote: > > The only irregularities I could find in this manual are multiple menu > > entries > > for the same node (in "Help-Inv" and "Help-M"). > > That manual's structure is not a tree. It is pretty close to being a tree, as far as I coul

Re: New structure warnings and deeply nested nodes in libc manual

On Sun, Jun 29, 2025 at 07:50:47AM +0300, Eli Zaretskii wrote: > > From: Gavin Smith > > Date: Sat, 28 Jun 2025 21:45:03 +0100 > > > > And now I have warnings with this manual (patch at the end of this mail): > > > > $ TEXINFO_XS_STRUCTURE=0 ../tta/perl/texi2any.pl info.texi > > info.texi:461: w

Re: New structure warnings and deeply nested nodes in libc manual

> From: Gavin Smith > Date: Sat, 28 Jun 2025 21:45:03 +0100 > > And now I have warnings with this manual (patch at the end of this mail): > > $ TEXINFO_XS_STRUCTURE=0 ../tta/perl/texi2any.pl info.texi > info.texi:461: warning: unexpected node `Help-]' in menu > info.texi:462: warning: unexpected

Re: New structure warnings and deeply nested nodes in libc manual

> From: Gavin Smith > Date: Sat, 28 Jun 2025 20:47:31 +0100 > Cc: pertu...@free.fr, bug-texinfo@gnu.org > > On Tue, Jun 24, 2025 at 02:28:44PM +0300, Eli Zaretskii wrote: > > As an example of a manual whose structure is not a tree, but is > > well-thought out, see info.texi. I'd expect to see su

Re: New structure warnings and deeply nested nodes in libc manual

On Sun, Jun 29, 2025 at 02:15:05AM +0200, pertu...@free.fr wrote: > > Patrice: the > > "$menu_node_relations->{'associated_section'}->{'section_directions'}->{'next'}->{'associated_node'}->{'element'}" > > stuff is very verbose. All this is doing is finding the next > > node based on sectioning.

Re: replacement for titlepage and more metadata commands

> > In the default case, when using @documentinfo, the copying text would be > > output > > on the verso of the title page in PDF output. No separate command would be > > necessary. > > It is necessary if the user wants a specific formatting different than > the default. Could we support input

Re: New structure warnings and deeply nested nodes in libc manual

On Sat, Jun 28, 2025 at 09:45:03PM +0100, Gavin Smith wrote: > And now I have warnings with this manual (patch at the end of this mail): > > $ TEXINFO_XS_STRUCTURE=0 ../tta/perl/texi2any.pl info.texi > info.texi:461: warning: unexpected node `Help-]' in menu > info.texi:462: warning: unexpected no

Re: wrong to use Index match in Info reader for the presence of index?

On Sat, Jun 28, 2025 at 10:02:06PM +0300, Eli Zaretskii wrote: > > Date: Sat, 28 Jun 2025 17:28:07 +0200 > > From: Patrice Dumas > > > Are you talking about info_indices_of_file_buffer? It does this: > > /* Grovel the names of the nodes found in this file. */ > if (file_buffer->tags) >

Re: New structure warnings and deeply nested nodes in libc manual

On Sat, Jun 28, 2025 at 08:47:33PM +0100, Gavin Smith wrote: > > As an example of a manual whose structure is not a tree, but is > > well-thought out, see info.texi. I'd expect to see such warnings > > there as well (unless the few explicit node pointers it has will avoid > > that), although the s

Re: wrong to use Index match in Info reader for the presence of index?

On Sat, Jun 28, 2025 at 08:53:22PM +0100, Gavin Smith wrote: > Yes, I believe I said this in another message. I'll try again to explain > how I think Info should find Info nodes: D'oh, I keep on saying "Info nodes", I meant "index nodes".

Re: wrong to use Index match in Info reader for the presence of index?

On Sat, Jun 28, 2025 at 10:23:59PM +0300, Eli Zaretskii wrote: > > From: Gavin Smith > > Date: Sat, 28 Jun 2025 19:54:36 +0100 > > > > I also don't think it is a huge restriction to have "Index" in the > > node name. Non-English Info manuals could have English node names, or > > they could have

Re: New structure warnings and deeply nested nodes in libc manual

On Tue, Jun 24, 2025 at 02:28:44PM +0300, Eli Zaretskii wrote: > > So while the Info output is basically fine, output that doesn't use > > menus, including the default HTML output and output with TeX, has > > problems. Hence I believe we should keep the new warnings with > > CHECK_NORMAL_MENU_STRU

Re: wrong to use Index match in Info reader for the presence of index?

> From: Gavin Smith > Date: Sat, 28 Jun 2025 19:54:36 +0100 > > I also don't think it is a huge restriction to have "Index" in the > node name. Non-English Info manuals could have English node names, or > they could have the word "Index" in addition to the translation. Info files that don't sup

Re: wrong to use Index match in Info reader for the presence of index?

> Date: Sat, 28 Jun 2025 17:28:07 +0200 > From: Patrice Dumas > > Hello, > > In the Info reader, the node name for "Index" is checked in addition to > the presence of an index (with (node->flags & N_IsIndex), and possibly > the presence of non empty menu). > > I think that it is wrong to do t

Re: wrong to use Index match in Info reader for the presence of index?

On Sat, Jun 28, 2025 at 07:32:04PM +0200, Patrice Dumas wrote: > On Sat, Jun 28, 2025 at 04:39:14PM +0100, Gavin Smith wrote: > > As I remember, the marker for an index node (^@^H[index^@^H]) was not > > added by older versions of texi2any/makeinfo. So there are Info files > > out there that do no

Re: wrong to use Index match in Info reader for the presence of index?

On Sat, Jun 28, 2025 at 04:39:14PM +0100, Gavin Smith wrote: > As I remember, the marker for an index node (^@^H[index^@^H]) was not > added by older versions of texi2any/makeinfo. So there are Info files > out there that do not have such a marker in Info nodes. Actually, there is a second reason

Re: replacement for titlepage and more metadata commands

On Thu, Jun 26, 2025 at 07:49:58PM +0100, Gavin Smith wrote: > Coming back to this thread as I was prompted by Patrice: > > https://lists.gnu.org/archive/html/bug-texinfo/2025-01/msg00066.html > > I don't have a complete proposal but will post some comments to help > get this conversation going a

Re: wrong to use Index match in Info reader for the presence of index?

On Sat, Jun 28, 2025 at 05:28:07PM +0200, Patrice Dumas wrote: > Hello, > > In the Info reader, the node name for "Index" is checked in addition to > the presence of an index (with (node->flags & N_IsIndex), and possibly > the presence of non empty menu). > > I think that it is wrong to do that

  1   2   3   4   5   6   7   8   9   10   >