lilypond-user
[Top][All Lists]
Advanced

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

Re: Forcing and preventing page-turns


From: David Wright
Subject: Re: Forcing and preventing page-turns
Date: Sun, 6 Nov 2016 07:42:40 -0600
User-agent: Mutt/1.5.21 (2010-09-15)

On Sun 06 Nov 2016 at 14:31:24 (+0100), Simon Albrecht wrote:
> On 06.11.2016 14:26, David Wright wrote:
> >On Sat 05 Nov 2016 at 21:25:07 (+0100), Urs Liska wrote:
> >>Am 05.11.2016 um 21:20 schrieb David Sumbler:
> >>>It always seems to be a bit hit-and-miss for me when I try to arrange
> >>>the pagination of instrumental parts.  Reading the manual it isn't
> >>>clear to me how I can force page turns to occur *only* at the points I
> >>>choose.
> >>\override Score.NonMusicalPaperColumn.line-break-permission = ##f
> >>
> >>will prevent any automatic breaks.
> >>
> >>>Also, Lilypond doesn't like ending on an even-numbered page.  How can I
> >>>force it not to add an unnecessary extra page at the end of a part?
> >>>  The reason is that the part in question can fit on to 12 pages.  I
> >>>don't want it extended to 13 because that means an extra sheet of paper
> >>>and 3 blank pages at the end of the part.
> >>I don't know if there's a way to automatically achieve what you want,
> >>but you can always force the actual number of pages with
> >>
> >>\paper {
> >>   page-count = 12
> >>}
> >(I've just rechecked the following with 2.19.49)
> >
> >My experience with page-count is that all too often it causes LP to
> >set early pages too slackly, and then overfills the last page.
> 
> Try a combination of page-count, system-count, systems-per-page,
> min-systems-per-page, max-systems-per-page. And if all of that
> doesn’t help, you might have to go to manual breaking.

Yes, I hadn't seen that entire armoury, so thanks for that.
But it did surprise me that you get such different results
when you tell it to do what it would have done anyway.

Cheers,
David.



reply via email to

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