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

2025-06-28 Thread Eli Zaretskii
> 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

2025-06-28 Thread Eli Zaretskii
> 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

2025-06-28 Thread Gavin Smith
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

2025-06-28 Thread Gavin Smith
> > 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

2025-06-28 Thread pertusus
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?

2025-06-28 Thread Patrice Dumas
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

2025-06-28 Thread Gavin Smith
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?

2025-06-28 Thread Gavin Smith
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?

2025-06-28 Thread Gavin Smith
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

2025-06-28 Thread Gavin Smith
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?

2025-06-28 Thread Eli Zaretskii
> 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?

2025-06-28 Thread Eli Zaretskii
> 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?

2025-06-28 Thread Gavin Smith
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?

2025-06-28 Thread Patrice Dumas
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

2025-06-28 Thread Patrice Dumas
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?

2025-06-28 Thread Gavin Smith
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

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

2025-06-28 Thread 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 that, firstly because having (node->flags & N_IsIndex) is more accurante, an Ind