lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Protecting against page breaks in markup


From: Flaming Hakama by Elaine
Subject: Re: Protecting against page breaks in markup
Date: Wed, 28 Nov 2018 18:08:15 -0800



On Wed, Nov 28, 2018, 1:50 AM Richard Shann <address@hidden wrote:
On Tue, 2018-11-27 at 16:33 -0800, Flaming Hakama by Elaine wrote:
> > ---------- Forwarded message ----------
> > From: Richard Shann <address@hidden>
> > To: lilypond-user <address@hidden>
> > Cc: 
> > Bcc: 
> > Date: Tue, 27 Nov 2018 15:20:04 +0000
> > Subject: Protecting against page breaks in markup
> > I'm creating an index to my scores, in the form of a sequence of
> > LilyPond markups (for title, composer, first few bars etc).
> > It is working well apart from page breaking which can occur mid-
> > entry.
> > Is there a way of turning page breaks off and back on around each
> > entry?
> >
> > Richard Shann
>
> When pagination gets hairy, I use \autoPageBreaksOff, and then
> manually put in all page breaks using \pageBreak

Sorry, I should have made it clearer that this index is being
automatically generated. Now you point out that there is an
\autoOageBreaksOff, which is what I thought I needed, I realize that it
wouldn't help - I would need to turn them off and back on between each
entry in the hope that LilyPond would take advantage of such an Off/On
sequence to insert a page break in between if needed, which I'm sure it
wouldn't :(

Richard

Yeah, once autoPageBreaksOff is declared, all page breaks need to be added manually.  

I've found that when the automatic page breaks don't work, it usually easier to go this way than the other alternative, which is to use auto page breaks and add noPageBreak where necessary. 

Mostly because forcing a no page break doesn't guarantee that the newly calculated automatic break will be in a good place, so you often end up adding lots of noPageBreak commands in close succession, and it ends up being more tedious and less semantic.

Also, page break calculations take up time, so using manual breaks speeds up compilation and saves time in the long run.

I'm not sure if when you say this is being automatically generated that it may be produced in different editions which need different page breaks. But even in that case it is probably easiest to use tags or something like the addition engraver to specify the page breaks.

You can also try putting scores in book Parts which have the effect of forcing a page break at the start of the book part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]