lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 3631 in lilypond: 2.17 does a worse job with v


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3631 in lilypond: 2.17 does a worse job with vertical spacing and/or the page layout than 2.16
Date: Fri, 01 Nov 2013 07:00:51 +0000


Comment #36 on issue 3631 by address@hidden: 2.17 does a worse job with vertical spacing and/or the page layout than 2.16
http://code.google.com/p/lilypond/issues/detail?id=3631

Just confirming that the patch does fix a real problem. Currently things like Clefs, that appear depending on line breaks, are ignored in page-break planning. If anyone does something like
 { \override Staff.Clef #'font-size = #6
   \repeat unfold 20 {R1 \break} }
the pages are overfull.  The patch fixes that problem.

It was surprising that allowing /more/ space for clefs made David's example take /fewer/ pages. Due to the unspeakable complexity of the 'part_of_line_pure_height' estimation for page-breaking, the BarNumber is placed against staff-lines-only of the top-most StaffSymbol, and the assumed position of the StaffSymbol in the System takes into account only the first measure in the tentative line. If there are no high notes in the first measure, the upper loop of the Clef moves the StaffSymbol down, and thus the BarNumber.

I regret wasting the time figuring out why, but the patch works.

Attachments:
        3631.png  6.5 KB

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

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