Can you at least provide the source code of squashed.pdf? It is a bit hard to troubleshoot code we can't read... feels like a House M.D episode.
Em qua., 3 de dez. de 2025 às 12:04, Pierre-Luc Gauthier < [email protected]> escreveu: > That leads me to another question though : Why, when there are > "over-full page by xx.x staff-spaces", why doesn't lilypond just add > more pages ? > > In the attached PDF (18.pdf) (a single page of a score) : of course I > get over-full pages and of course Lily can't do much more than squash > the music. But, on the second PDF (squashed.pdf) why oh why can't it > push the music over the next page (moreover on two facing pages) ? > > Just for fun, I've -dembed-source-code. I often include the code in > the PDF but never actually tried to compile it... The file to compile > is parts-book-template-working.ily > > Le mar. 2 déc. 2025, à 09 h 05, Carl Sorensen > <[email protected]> a écrit : > > > > On Tue, Dec 2, 2025 at 8:29 AM Pierre-Luc Gauthier > > <[email protected]> wrote: > > > > > > I've not managed to produce a MWE yet but I am trying. > > > > > > > Sorry, I missed the point that the problem seems to involve the > > Page_turn_engraver. > > > > Have you looked at the properties that affect the operation of the > > Page_turn_engraver? > > > > > https://lilypond.org/doc/v2.25/Documentation/internals/page_005fturn_005fengraver > > > > Perhaps you could try changing the values of > > pageTurnMinimumRepeatLength and/or pageTurnMinimumRestLength. (Note > > that the names are different in 2.24) > > > > These rules limiting page turns could potentially cause problems when > > you have rests in the staves but music in the ChordNames context -- > > the music in the ChordNames context doesn't have rests so it could > > prevent page turns. > > > > I'm basically shooting in the dark as I don't have any source files. > > I'm just looking for any reasons I can think of for making such > > overfull pages. > > > > -- > Pierre-Luc Gauthier >
