Comment #8 on issue 22 by gra...@percival-music.ca: collision tuplet number
and staff with increased spacing
http://code.google.com/p/lilypond/issues/detail?id=22
Still looks like it collides with #0.9
___
bug-lilypond mailing list
bug-lilypond@gn
Updates:
Owner: ---
Labels: -Priority-Low
Comment #7 on issue 22 by pkx1...@gmail.com: collision tuplet number and
staff with increased spacing
http://code.google.com/p/lilypond/issues/detail?id=22
Attached is the output from 2.15.29 using
\version "2.15.29"
\new Staff \with
Comment #5 on issue 22 by a...@arnowaschk.de: collision tuplet number and
staff with increased spacing
http://code.google.com/p/lilypond/issues/detail?id=22
In 2.13.3 it seems to me staff line is avoided at many different staff-space
numbers, at least for the given example. FYI
--
You receiv
Issue 22: collision tuplet number and staff with increased spacing
http://code.google.com/p/lilypond/issues/detail?id=22
Comment #4 by v.villenave:
(Reproduced with 2.11.47)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this
Issue 22: collision tuplet number and staff with increased spacing
http://code.google.com/p/lilypond/issues/detail?id=22
Comment #3 by gpermus:
That's a coincidence. Change the number to #1.3 and you'll see a collision.
--
You received this message because you are listed in the owner
or CC fi
Issue 22: collision tuplet number and staff with increased spacing
http://code.google.com/p/lilypond/issues/detail?id=22
Comment #2 by horndude77:
This issue might have been fixed. At least the example seems fixed. I
just tried it
with 2.11.37 and the '3' is now placed in the top space between t
