Comment #26 on issue 2397 by [email protected]: Tuplet number incorrectly
placed when using additonal articulations and/or abreak
http://code.google.com/p/lilypond/issues/detail?id=2397
Looks good.
Just to be clear, the patch retreats from completely resolving
tuplet/script collisions, issues 256 and 1361. When there is /both/ a
tuplet and a slur, LilyPond never got the tuplet placement right.
After this patch, LilyPond will not try to resolve tuplet/script collisions
where there is a slur (image attached is comment 14 with \voiceOne) which
is certainly better than putting the tuplet number in the middle of the
staff.
Without the complication of a slur, tuplet/script collisions are resolved.
Attachments:
no_worse_than_before.png 5.8 KB
