On Thu, 2010-06-24 at 14:05 +0200, Arno Waschk wrote:
On Sun, 20 Jun 2010 18:41:47 +0200, Joe Neeman <address@hidden>
wrote:
> On Sun, 2010-06-20 at 16:19 +0200, Arno Waschk wrote:
>> dear list,
>>
>> the following:
>>
>>
>> \version "2.13.23"
>> \include "deutsch.ly"
>> TempoMark={ \time 4/4 \repeat unfold 20 {s1*5 \mark \default} }
>>
>> celloPart = \new Staff \with {} { \relative c''{ \repeat unfold 19
>> {\repeat unfold 5{c8[c c c c c c c]}
>> \mark "BLABLA"
>> } c1 }}
>>
>> rechtsPart = \new Staff \with {} {\relative c'{ \repeat unfold 399
{c4}
>> f4 }}
>>
>> linksPart = \relative c, {s1*100}
>> #(set-global-staff-size 22.5)
>> \score {
>> <<
>> \celloPart
>> \rechtsPart
>> >>
>> \layout {
>> \context{\RemoveEmptyStaffContext
>> \override VerticalAxisGroup #'remove-first = ##t
>> } } }
>>
>> gives here (latest lilypond from git as of 20th June 2010 3pm MESZ)
the
>> problem of three warnings "couldn't fit music on page",
>> and the last systems of page 2 and 3 being cut off by the lower end
of
>> the
>> paper.
>>
>> this disappear when one either comments out the "\mark ..." line, or
>> uses
>> lilypond 2.12.
>>
>> this seems like a regression bug, no?
>>
>> could not yet find something similar on the issue tracker.
>
> I'm pretty sure this is an instance of bug 1062.
>
> Cheers,
> Joe
>
Hi, is there a workaround other than downgrading to 2.13.18?
You can always use page-breaking-between-system-spacing to fool the page
breaker into using more pages:
\paper {
page-breaking-between-system-spacing #'padding = #5
}
Or you can set max-systems-per-page, or add a manual page break. Or you
can wait until 2.13.26, since the bug is fixed in git.
I mean, couldn't Lilypond easily push the last line on the next page
when
the "couldn't fit music on page" warning is issued, until the whole
thing
is solved completely?
In specific situations, maybe, but lilypond can't do it in general
without breaking \pageBreak, min-systems-per-page, page-count and other
commands.
The annotate-spacing output (for me) seems to show that lilypond is
aware
of correct spacing anyway...
Yes, but we don't know the _exact_ height of each system until after
page-breaking is done (otherwise, we would have to do all the layout for
every conceivable page-breaking solution and that would take far too
long).
Cheers,
Joe