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

[lilypond]

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

It looks like this was the problem reported on -user,
now at  
<https://lists.gnu.org/archive/html/bug-lilypond/2013-05/msg00009.html>

The original example hid a tempo mark with 'tempoHideNote'.  The example  
below shows the page-breaker estimates before and after the change for  
issue 3279.   The extent-estimate is the height of the staff estimated for  
page-breaking; the staff and its notes extend from 0 down to -7.6.

Before tempo-spacing (image left) the tempo marks were assumed to sit on  
top of the staff-lines, so there is no allowance for the tempo.  After  
tempo-spacing (image right) the tempo marks are assumed to sit on top of  
the highest notes on the line-broken line (calculated for each tentative  
line-break solution) *plus* a little bit to clear any padding applied at  
the note-spacing step.  (If there are several tempo marks on a line they  
are assumed to set beside each other, not on top of each other, and their  
estimated heights do not accumulate.)

The allowance is too small before the patch for issue 3279, and in the  
special case of an empty tempo mark, too much after the issue 3279 patch by  
the amount of the padding and extra allowance.   The patch above for this  
issue cuts the extra 1.5 staff-space down to 0.8 staff-space.

\paper{annotate-spacing = ##t ragged-right = ##t
 indent = 2\cm short-indent = \indent }
{ \clef bass
  \tempo "Vif" 2=80 g'1 \break
  \tempo 2=80 g'1 \break
  \set Score.tempoHideNote = ##t
  \tempo "Vif" 2=80 g'1 \break
  \tempo 2=80 g'1 }


Attachments:
        3342.png  58.0 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