Comment #37 on issue 3831 by [email protected]: Patch: Improve
positioning of tuplet numbers for kneed beams.
http://code.google.com/p/lilypond/issues/detail?id=3831
Oh, I see what happened. You must be looking at the version
with 'knee-to-beam set to #f: the older LilyPond default. Then I get major
collisions. This makes the old behavior look even worse! (I opted to go
for something not-too-terrible.)
Maybe I should reverse the order of examples? So we get a before=with
knee-to-beam set to #f = bad, followed by the corrected version?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
