Re: texinfo 7.0.3; the main menu is missing in HTML output.
Hello, Gavin.
On Mon, Aug 14, 2023 at 16:11:32 +0100, Gavin Smith wrote:
> On Tue, Aug 08, 2023 at 01:17:06PM +, Alan Mackenzie wrote:
> > On Mon, Aug 07, 2023 at 23:25:42 +0100, Gavin Smith wrote:
> > > On Mon, Aug 07, 2023 at 09:16:36PM +, Alan Mackenzie wrote:
> > [ ]
> > > To get the menus output in HTML, use the FORMAT_MENU variable. It
> > > would look like "texi2any -c FORMAT_MENU=menu my-manual.texi".
> > Thanks for such a rapid and helpful reply! That works!
> > I don't think there's a link to this option from the manual section on
> > @menu, though.
> > [ ]
> I've reworded it and added a cross-reference:
> --- a/doc/texinfo.texi
> +++ b/doc/texinfo.texi
> @@ -2831,9 +2831,10 @@ @node Menus
> @findex menu
> @dfn{Menus} contain pointers to subordinate nodes. In Info output,
> -you use menus to go to such nodes. Menus can be used in HTML output
> -but are not used in the default case. Menus have no role in printed
> -manuals or other output formats.
> +you use menus to go to such nodes. @command{texi2any} can output menus in
> +HTML output, but does not do so by default
> +(@pxref{Other Customization Variables}, under @code{FORMAT_MENU}).
> +Menus have no role in printed manuals or other output formats.
> Menus are automatically generated by @command{texi2any} when outputting
> Info for nodes followed by a sectioning command, without an explicit
OK. Thanks!
--
Alan Mackenzie (Nuremberg, Germany).
Re: texinfo 7.0.3; the main menu is missing in HTML output.
On Tue, Aug 08, 2023 at 01:17:06PM +, Alan Mackenzie wrote:
> Hello, Gavin.
>
> On Mon, Aug 07, 2023 at 23:25:42 +0100, Gavin Smith wrote:
> > On Mon, Aug 07, 2023 at 09:16:36PM +, Alan Mackenzie wrote:
>
> [ ]
>
> > To get the menus output in HTML, use the FORMAT_MENU variable. It
> > would look like "texi2any -c FORMAT_MENU=menu my-manual.texi".
>
> Thanks for such a rapid and helpful reply! That works!
>
> I don't think there's a link to this option from the manual section on
> @menu, though.
>
> [ ]
I've reworded it and added a cross-reference:
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -2831,9 +2831,10 @@ @node Menus
@findex menu
@dfn{Menus} contain pointers to subordinate nodes. In Info output,
-you use menus to go to such nodes. Menus can be used in HTML output
-but are not used in the default case. Menus have no role in printed
-manuals or other output formats.
+you use menus to go to such nodes. @command{texi2any} can output menus in
+HTML output, but does not do so by default
+(@pxref{Other Customization Variables}, under @code{FORMAT_MENU}).
+Menus have no role in printed manuals or other output formats.
Menus are automatically generated by @command{texi2any} when outputting
Info for nodes followed by a sectioning command, without an explicit
Re: texinfo 7.0.3; the main menu is missing in HTML output.
Hello, Gavin. On Mon, Aug 07, 2023 at 23:25:42 +0100, Gavin Smith wrote: > On Mon, Aug 07, 2023 at 09:16:36PM +, Alan Mackenzie wrote: [ ] > To get the menus output in HTML, use the FORMAT_MENU variable. It > would look like "texi2any -c FORMAT_MENU=menu my-manual.texi". Thanks for such a rapid and helpful reply! That works! I don't think there's a link to this option from the manual section on @menu, though. [ ] -- Alan Mackenzie (Nuremberg, Germany).
Re: texinfo 7.0.3; the main menu is missing in HTML output.
On Mon, Aug 07, 2023 at 09:16:36PM +, Alan Mackenzie wrote: > Hello, help-texinfo. > > In texinfo-7.0.3, my main menu (a long menu starting with @menu and > ending with @end menu) is not getting output in my HTML output. This is > failing to happen even with an older version of my .texi file which > previously generated an HTML main menu under an earlier version of > texinfo. > > On page "menus" in the texinfo manual appears: > > "Menus" contain pointers to subordinate nodes. In Info output, you use > menus to go to such nodes. Menus can be used in HTML output but are not > used in the default case. Menus have no effect in printed manuals and > do not appear in them. Menus are ignored in DocBook output. > > which I find confusing. The first occurrence of "use" is talking about a > user using a menu whilst reading an Info document. The next sentence, > sadly in the passive voice, says "Menus ... in HTML output ... are not > used in the default case". What does this sentence mean? Who or what is > doing this "using" and what is the nature of this use? Yes, the passive voice can be confusing and this text could be reworded. To get the menus output in HTML, use the FORMAT_MENU variable. It would look like "texi2any -c FORMAT_MENU=menu my-manual.texi". > > Does this sentence mean that @menu ... @end menu by default produces no > output in HTML? After a long frustrating search, I could find no > directions to override this default, if that's what it means. > > Please help me get my main menu back again in HTML! > > Thanks! > > -- > Alan Mackenzie (Nuremberg, Germany). >
