On 29-Aug-05, at 10:01 AM, Erik Sandberg wrote:
Citerar Han-Wen Nienhuys <[EMAIL PROTECTED]>:
Graham Percival wrote:
Lilypond 2.7 no longer creates linebreaks to avoid text running off
the
page.
Check out the keep-inside-line property.
Ah, ok. I guess that in the past this was #t by default.
When switched on, it becomes a
bottleneck as it adds a quadratic number of constraints for each
spaced
line.
By "bottleneck", do you mean a speed bottleneck? I find that it adds
about
7% to the compile time. IMO that's quite worth it[1], so I suggest
that it be
turned on by default. But as long as it's documented, it doesn't
really matter
what the default is.
[1] admittedly it's only worth it in a score which has textScripts, and
some
scores don't.
IWBN if there was a list of properties that are turned off only for
performance
reasons. Some users might not have speed as their biggest concern,
those could
want to turn on all such properties.
Yes, absolutely. Or even have a general command that turned them all
on?
\fastMusic = {
\override Score.PaperColumn #'keep-inside-line = ##f
etc
}
\qualityMusic = {
\override Score.PaperColumn #'keep-inside-line = ##t
etc
}
Alternately we could just have a few manual pages about the various
options you can turn on (or off) to fiddle with the speed/beauty ratio.
Cheers,
- Graham
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
