Re: ugly page break in ToC

2025-07-07 Thread Werner LEMBERG
>> Thanks, this helps: for my version of the LilyPond Notation >> Reference a value of 10pt works just fine. Before that I tried >> 20pt, however, I got a different but equally bad gap as reported >> originally. This makes me wonder whether we are we really turning >> the right screw... > > I tr

Re: ugly page break in ToC

2025-07-07 Thread Werner LEMBERG
>> While playing around with adding parts to LilyPond's Notation >> Reference, I got the attached layout in the ToC. As can be seen, >> there is a vertical gap corresponding to approx. 8 lines(!) at the >> bottom of page vi; I've never noticed such a large gap before in any >> Texinfo document. [

Re: better PDF formatting of `@part` in ToC

2025-07-07 Thread Werner LEMBERG
>> I played around a bit more, and I think it looks good if the >> vertical space right before the part entry gets increased a bit, >> see attached image. > > I think it will be safest to keep the same size for the text, > and just to use increased spacing before the part line to separate > it v

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

2025-07-07 Thread Gavin Smith
On Sun, Jun 29, 2025 at 11:55:11PM +0200, Patrice Dumas wrote: > On Sat, Jun 28, 2025 at 07:54:36PM +0100, Gavin Smith wrote: > > > I checked that a tag that is not 'Node:' or 'Ref:' has the Info reader > > > (but not the Emacs Info reader) stop going through tags immediatly. > > > This means that

Re: ugly page break in ToC

2025-07-07 Thread Gavin Smith
On Mon, Jul 07, 2025 at 06:10:52AM +, Werner LEMBERG wrote: > > [texinfo.tex 2025-03-22.08] > [luatex Version 1.22.0 (TeX Live 2025), Development id: 7673] > > > While playing around with adding parts to LilyPond's Notation > Reference, I got the attached layout in the ToC. As can be seen,

Re: better PDF formatting of `@part` in ToC

2025-07-07 Thread Werner LEMBERG
> Since `@part` is outside of the sectioning hierarchy I suggest to > not indent it at all, see the second attached image; doing so has > the additional bonus that it sticks out more prominently – right > now, because it uses the same font and size as ToC entries for > `@chapter`, it can be easily