Updates:
Status: Verified
Comment #5 on issue 496 by v.villenave: page-splitting calculation needs
work
http://code.google.com/p/lilypond/issues/detail?id=496
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of th
Comment #4 on issue 496 by joeneeman: page-splitting calculation needs work
http://code.google.com/p/lilypond/issues/detail?id=496
I've added page-breaking-good-estimation.ly
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this
Updates:
Labels: -Type-Defect Type-Documentation Maintainability
Comment #3 on issue 496 by v.villenave: page-splitting calculation needs
work
http://code.google.com/p/lilypond/issues/detail?id=496
Do we need a regtest for this? (since page-breaking stuff might change in
the future)
Updates:
Status: Fixed
Labels: fixed_2_13_1
Comment #2 on issue 496 by joeneeman: page-splitting calculation needs work
http://code.google.com/p/lilypond/issues/detail?id=496
(No comment was entered for this change.)
--
You received this message because you are listed in the own
Issue 496: page-splitting calculation needs work
http://code.google.com/p/lilypond/issues/detail?id=496
Comment #1 by joeneeman:
This is caused by the fact that the height-estimation procedures
over-estimate the
height of each system (as can be seen by adding annotate-spacing = ##t
to the paper
Issue 496: page-splitting calculation needs work
http://code.google.com/p/lilypond/issues/detail?id=496
New issue report by gpermus:
% sorry about the lame summary; I couldn't think of anything better. :(
%% The page breaking algorithm doesn't calculate well.
%%
%% LilyPond thinks that the foll
