Re: [Lilypond-auto] Issue 3631 in lilypond: 2.17 does a worse job with vertical spacing and/or the page layout than 2.16

[lilypond]

Updates:
        Cc: address@hidden address@hidden

Comment #27 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

Re: comment 26
Since version 2.11.x, while choosing line-breaks, LilyPond looks ahead at  
the likely page-breaking.

The default 'optimal-breaking' method considers several line-breaking  
solutions, each time with a different constraint on the total number of  
systems.  For each, page-breaks are chosen using estimated heights of  
systems, and a combined score for horizontal and vertical fit is made.  The  
set of line&page breaks with the beat overall fit is chosen.  Then the  
graphical elements are laid out on each line, causing various Y-offset to  
take their real (unpure) values.

LilyPond does not alter the page-break choices from those made in the  
estimation step.

(I do not like this system myself, and never use the default breaker.   
<http://lists.gnu.org/archive/html/lilypond-user/2013-05/msg00774.html> )

BarNumbers, MetronomeMarks, and RehearsalMarks are engraved at the Score  
level, so during line&page breaking they should be placed against the  
entire System.  As I recall, the estimator for 'pure' system height up to  
2.16-ish included only the bare StaffSymbols, and did not descend to  
include all the elements on the staves.  This was reasonable since these  
marks can generally be placed against the bare staff.

The patch linked to comment 24 would seem to include the clef in the box,  
that the BarNumbers are placed over for purposes of page-break-estimates.   
BarNumbers do not usually sit over the clef.  The patch seems to address  
the contrived example of comment 16, and not the (contrived) example at the  
top of this issue.

--
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