Comment #5 on issue 1043 by k-ohara5...@oco.net: beams no longer count
towards boundary boxes
http://code.google.com/p/lilypond/issues/detail?id=1043
The issue occurs in stable 2.12.3 as well. Short example input attached.
Produced by staff-crossing either a) within or adjacent to an
Comment #4 on issue 1043 by joeneeman: beams no longer count towards
boundary boxes
http://code.google.com/p/lilypond/issues/detail?id=1043
It's because of the way beam creation interacts with cross-staff stuff. The
beam in the third beat is marked as cross-staff because it is created
Comment #2 on issue 1043 by Carl.D.Sorensen: beams no longer count towards
boundary boxes
http://code.google.com/p/lilypond/issues/detail?id=1043
I don't think the last two notes pull the upper skyline down. The upper
skyline goes along the top of the staff
line. The last two notes pull
Comment #1 on issue 1043 by n.puttock: beams no longer count towards
boundary boxes
http://code.google.com/p/lilypond/issues/detail?id=1043
Valentin's pointed out another example from input/regression on lilywiki:
fingering-cross-staff.ly
It seems to me there's a skylining problem here;
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1043 by percival.music.ca: beams no longer count towards boundary
boxes
http://code.google.com/p/lilypond/issues/detail?id=1043
music images in the HTML boxes for NR 1.1.3 Automatic accidentals have a
beam being clipped
