Re: Issue 582 in lilypond: slur and tie start in (almost) same spot

2011-09-30 Thread lilypond
Updates: Status: Accepted Labels: -fixed_2_15_13 Comment #3 on issue 582 by k-ohara5...@oco.net: slur and tie start in (almost) same spot http://code.google.com/p/lilypond/issues/detail?id=582 Oops, not fixed. We now have to say ragged-right = ##f to see the problem. ___

Re: Issue 582 in lilypond: slur and tie start in (almost) same spot

2011-09-30 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_15_13 Comment #2 on issue 582 by k-ohara5...@oco.net: slur and tie start in (almost) same spot http://code.google.com/p/lilypond/issues/detail?id=582 Fixed sometime before 2.15.13 (maybe by Mike, or maybe Reinhold?)

Issue 582 in lilypond: slur and tie start in (almost) same spot

2008-05-30 Thread codesite-noreply
Issue 582: slur and tie start in (almost) same spot http://code.google.com/p/lilypond/issues/detail?id=582 Comment #1 by v.villenave: It looks the same with 2.11.47 (except that you have to specify ragged-right = ##f to see it happening). However, I'm not sure there has to be a better way (I r

Issue 582 in lilypond: slur and tie start in (almost) same spot

2008-02-27 Thread codesite-noreply
Issue 582: slur and tie start in (almost) same spot http://code.google.com/p/lilypond/issues/detail?id=582 New issue report by wbsoft: \version "2.11.41" %{ The slur and the tie start in (almost) the same spot. Only when spacing very tightly (uncomment the \paper line) it looks better. %} %\pap