Re: [Lilypond-auto] Issue 3342 in lilypond: page breaking regression

[lilypond]

Comment #8 on issue 3342 by address@hidden: page breaking regression
http://code.google.com/p/lilypond/issues/detail?id=3342

The bug reported in the email linked to comment 6 used something like
<<\new Staff \with {
    \RemoveEmptyStaves
    \override VerticalAxisGroup #'remove-first = ##t
  } R1*6
  \new Staff { \clef bass
  \tempo "Vif" 2=80 g1 \break
  \tempo 2=80 g1 \break
  \set Score.tempoHideNote = ##t
  \tempo "Vif" 2=80 g1 \break
  \tempo 2=80 g1 } >>
During page-breaking planning the staff with the notes is pushed down by  
the minimum-distance to the empty staff above. Annotate-spacing shows the  
staves at negative positions. The \tempo mark is at the top of the System,  
at positive positions, and the estimated height of each System is  
overestimated by one minimum-distance between staves.

The patch in comment 7 goes back to the old way of sliding the \tempo down  
against the uppermost staff-symbol, before figuring horizontal spacing.    
This patch supplies \markLengthOn as an option, not default, implemented in  
a less-pretty way that raises \tempo 4 spaces for horizontal-spacing  
purposes only, without increasing the system-height estimates for  
page-breaking.  It is still a good thing to do, so I'll repeat the link
http://codereview.appspot.com/9210044

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