Joe Neeman wrote:
I'm just worried that the algorithm will have to deal with scores that have almost no viable breaks. Either we allow breaks at practically every rest (with huge penalties) or we don't have enough break points. The first solution will have very poor performance, and the second solution is also obviously not good. But maybe there is a better way to ensure good performance.
I don't understand why this is a problem. If there are no viable breaks, every configuration is as bad, and the algorithm should tend to the one which uses spacing that is as natural as possible, since that one should be the best among the configurations with no specially good page breaks.
-- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
