Matthew wrote:
Erik Sandberg erik.sandberg.9195 at student.uu.se writes:
This is a known problem. You can change Timing.measurePosition as a
workaround.
Erik
Is there any update to this problem? I ran into it last night; I worked around
it by creating an anacrusis the same
Issue 596: collision tuplet number and slur
http://code.google.com/p/lilypond/issues/detail?id=596
New issue report by v.villenave:
% The slur may collide with the tuplet number with following conditions:
% -tuplet is beamed
% -the slur is on the same side as the tuplet number
% -the slur starts
2008/4/2, Risto Vääräniemi [EMAIL PROTECTED]:
The slur may collide with the tuplet number with following conditions:
-tuplet is beamed
-the slur is on the same side as the tuplet number
-the slur starts or ends at the horizontal position of the tuplet number
(such a tuplet is usually a
Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #52 by asky314159:
Beyond that, all of the Intel command line binaries themselves do not
function. They all error, saying can not
execute binary file. The PPC command line binaries
