Hi Andrew, 2008/10/20 Andrew Hawryluk <[EMAIL PROTECTED]>: > I'm not upgrading my copy of Finale this year, so I'd like to > contribute some cash to fixing bugs 379 and 427: > http://code.google.com/p/lilypond/issues/detail?id=379 > http://code.google.com/p/lilypond/issues/detail?id=427 > > All it will take is getting slurs that cross a line break to begin > after the front matter (key signature, etc.) rather than before. > Phrasing slurs already do this properly, so I'm pretty sure that the > solution lies in changing something in slur-engraver.cc to match > phrasing-slur-engraver.cc.
I've tried fixing this (I find it one of the most annoying bugs in LilyPond; #379 was my first bug report), but it's not as simple as it first appears: slurs have to avoid breakable objects in the middle of a system, whereas phrasing slurs are assumed to live outside slurs (hence benefit from slur avoidance behaviour). I've attached a picture which shows the difference between the two: the slur avoids the time signature, whereas the phrasing slur goes straight through. Making slurs match phrasing slurs isn't an option here; the slur encompassing code needs to distinguish between prefatory matter and the same items placed elsewhere. Regards, Neil
<<attachment: slur-encompass.png>>
_______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
