Folks,
for technical reasons we use `texi2any` version 6.8 in LilyPond, not
wanting to upgrade to version 7.2 right now. There is a difference in
behaviour regarding automatically generated `@menu` blocks, and I
wonder whether it is possible to achieve the desired result with some
extra code or additional configuration in an init file using the older
version.
Consider this input file, `menu.texinfo`.
```
\input texinfo
@node Top
@top Top
@menu
* Foo:: Foo foo foo.
* Bar:: Bar bar bar.
@end menu
@node Foo
@chapter Foo
Foo
@node Bar
@chapter Bar
Baz
@node Bar-Foo
@section Bar-Foo
Bar-Foo
@node Bar-Bar
@section Bar-Bar
Bar-Foo
@bye
```
As can be seen, there is a single, hand-crafted, top-level `@menu`
block that has some additional descriptions. There is no menu block
within chapter `Bar`.
The test call is
```
texi2any --html -c FORMAT_MENU=menu menu.texinfo
```
which works just fine with version 7.2. However, with version 6.8,
there is no automatically generated menu in chapter `Baz` (see
attached images) – I guess this is a bug that has been fixed in newer
versions.
Is there any way to get the desired result with version 6.8? I tried
to use `-c FORMAT_MENU=sectiontoc` – in LilyPond, we have the complete
index in a side panel, so this solution would be acceptable to a
certain degree – however, it completely ignores manually generated
`@menu` blocks...
Werner
