Joe Neeman <joenee...@gmail.com> writes:
> On Wed, Aug 3, 2011 at 10:37 PM, David Kastrup <d...@gnu.org> wrote:
>> David Kastrup <d...@gnu.org> writes:
>>
>>> Joe Neeman <joenee...@gmail.com> writes:
>>>
>>>>> So I have several questions:
>>>>>
>>>>> - Is the behaviour I am experiencing (a system spilling over onto a
>>>>> second page) correct or a bug? If correct, what's the best way to
>>>>> avoid the spillage?
>>>>
>>>> \paper {
>>>> ragged-last-bottom = ##f
>>>> }
>>>>
>>>> By default, ragged-last-bottom is ##t, so lilypond has no incentive to
>>>> avoid that dangling system on page 2.
>>>
>>> I don't understand this "so".
>>>
>>> The following should still be penalized since they are deficiencies even
>>> on a ragged bottom:
>>>
>>> a) a page which is considerably less full than the previous page
>>> b) every page break, and most certainly inside of a system, should carry
>>> a penalty, giving Lilypond some incentive to compress systems iff it
>>> helps to avoid using more pages than necessary.
>>
>> Otherwise, the scoring does not care whether we have 5 pages with just a
>> single system and lots of bottom space, one full page, and 5 pages with
>> just a single system again.
>
> No, we penalize under-full pages (except for the last one), even when
> ragged-bottom is ##t. And we certainly don't want part (a) above when
> ragged-last-bottom is ##t. The whole point of ragged-last-bottom is
> that the last page is allowed to be very under-filled.
I disagree. The point of ragged-last-bottom is to tell Lilypond how to
format the last page when there is not enough material to be found. It
does not tell Lilypond that having little material is a good idea: that
is a separate concept.
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
