On Tue, Jan 07, 2025 at 03:08:38AM +0100, Patrice Dumas wrote: > On Mon, Jan 06, 2025 at 07:33:45AM +0000, Werner LEMBERG wrote: > > > > [texinfo 7.2] > > > > > > The documentation in the 'Direction' section of 'texi2any_api' says > > > > _Index_ > > The first output unit with ‘@printindex’. > > > > This is not ideal. Assuming that a large document has multiple > > indices, the most general index is normally the last one, not the > > first. > > It seems to me that it is more natural to use the first index, whatever > type it is, and it is more robust, the specified index may not exist or > be merged into another one.
If I understand correctly the issue is with the "Index" link that is generated in the HTML output and that there is no way to configure which index this refers to. This could be allowed with two options: * One to suppress the default "Index" link * Another to add a link to all pages to a certain node. This link would be expressed in terms of node (e.g. "Concept Index"), not index (e.g. "cp"). In July 2024, a user expressed a desire to add a "Top" link to the navigation bar for all pages: > == 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 experimented with several options but > didn't get this effect. Is something like this possible, and if not, > would it be a useful addition? Frederico Muñoz, 2024-07-17 https://lists.gnu.org/archive/html/bug-texinfo/2024-07/msg00002.html This appears to be exactly the same problem. I think we should support both links to pages in the Texinfo system as well as arbitrary URLs in header links. It could be done with some option to texi2any, like texi2any --html "--nav-button=Index=Concept Index" for a Texinfo node, or texi2any --html "--nav-button=Home=https://myhomepage.example.com/"; for an arbitrary webpage. (I feel like we may have discussed this before although I couldn't find any specific emails on the topic.) Is there anything else about the nav bar that should also be easily customizable that isn't currently? I prefer to allow this kind of customization, especially for functionality that is of a wide interest, through options or variables, rather than the customization API, as the former would be easier for users and also less likely to break.
