Re: Issue 39 in lilypond: collision flag notehead with polyphony

2012-01-26 Thread lilypond
Comment #12 on issue 39 by elu...@gmail.com: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 here is another quite frequent flag notehead collision: \relative c' { 8 } Attachments: test2.png 10.9 KB

Re: Issue 39 in lilypond: collision flag notehead with polyphony

2011-12-08 Thread lilypond
Updates: Labels: -Priority-High Comment #11 on issue 39 by pkx1...@gmail.com: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 (No comment was entered for this change.) ___ bug-lilypond mailing l

Re: Issue 39 in lilypond: collision flag notehead with polyphony

2011-10-03 Thread lilypond
Updates: Labels: -Patch-needs_work Patch-abandoned Comment #10 on issue 39 by colinpkc...@gmail.com: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 (No comment was entered for this change.) ___

Re: Issue 39 in lilypond: collision flag notehead with polyphony

2011-06-26 Thread lilypond
Comment #8 on issue 39 by philehol...@googlemail.com: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 Connor Harris has produced another example of colliding flags and noteheads: \relative c''{ << {c4 b a2} \\ {g'4 f8\noBeam f e2} >> \noBreak

Re: Issue 39 in lilypond: collision flag notehead with polyphony

2011-06-01 Thread lilypond
Comment #7 on issue 39 by lemniska...@gmail.com: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 Shouldn't shortening the flag be the desired solution? As we're going to have plenty of shortened flags available, this may be the most elegant one.

Re: Issue 39 in lilypond: collision flag notehead with polyphony

2011-01-28 Thread lilypond
Updates: Labels: -Patch Patch-needs_work Comment #6 on issue 39 by percival.music.ca: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 Mike, was your patch in comment 3 a serious one? I'm not certain where we stand on this particular issu

Re: Issue 39 in lilypond: collision flag notehead with polyphony

2011-01-10 Thread lilypond
Comment #5 on issue 39 by k-ohara5...@oco.net: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 Unfortunately, the horizontal shift to the left obscures the intent of simultaneous notes. Simultaneous noteheads are usually placed as closely as p

Re: Issue 39 in lilypond: collision flag notehead with polyphony

2011-01-10 Thread lilypond
Updates: Labels: Patch Comment #4 on issue 39 by neziap: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 39 in lilypond: collision flag notehead with polyphony

2011-01-07 Thread lilypond
Comment #3 on issue 39 by mtsolo: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 Potential fix offered - changes via slight horizontal shift. Attachments: 0001-Potential-fix-for-issue-39.patch 1.6 KB issue39after.png 9.7 KB _

Re: Issue 39 in lilypond: collision flag notehead with polyphony

2010-01-18 Thread lilypond
Updates: Owner: --- Labels: -Priority-Low Priority-High Comment #2 on issue 39 by percival.music.ca: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 (No comment was entered for this change.) Attachments: foo.preview.png 1.

Issue 39 in lilypond: collision flag notehead with polyphony

2008-05-30 Thread codesite-noreply
Issue 39: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 Comment #1 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. You may ad