> 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
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
>> 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
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
>> 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
Currently running "info texinfo menu" with the current output from
texinfo.texi does not go to the node you expect ('Menus'), but to the
documentation of the Info format instead ('Info Format Menu').
Likewise, "info texinfo image" goes to 'Info Format Image', not 'Images',
and "info texinfo printi
>> 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
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
>> 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
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
10 matches
Mail list logo
