Re: Issue 1059 in lilypond: left-over strings in bibliography

Updates: Status: Verified Comment #13 on issue 1059 by colinpkc...@gmail.com: left-over strings in bibliography http://code.google.com/p/lilypond/issues/detail?id=1059 Yes, it *does* look better, certainly more consistent. ___ bug-lilypond

Re: Issue 1450 in lilypond: Collision between slur and text in les-nereides regtest

Updates: Status: Verified Comment #5 on issue 1450 by colinpkc...@gmail.com: Collision between slur and text in les-nereides regtest http://code.google.com/p/lilypond/issues/detail?id=1450 verified 2.13.54 ___ bug-lilypond mailing list bug

Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style)

Comment #6 on issue 897 by n.putt...@gmail.com: key signatures should be inherited by all Voices (no matter their accidental style) http://code.google.com/p/lilypond/issues/detail?id=897 Patch LGTM, and passed `make check'. My only concern is that we don't really cover accidental styles very

Re: Issue 649 in lilypond: Let accidentals on tied notes across a break be valid for subsequent notes

Updates: Summary: Let accidentals on tied notes across a break be valid for subsequent notes Comment #8 on issue 649 by n.putt...@gmail.com: Let accidentals on tied notes across a break be valid for subsequent notes http://code.google.com/p/lilypond/issues/detail?id=649 Erm, you've turned

Re: Issue 1518 in lilypond: DOC: add explanation of part combine functions

Updates: Labels: -Patch-needs_work Patch-review Comment #5 on issue 1518 by colinpkc...@gmail.com: DOC: add explanation of part combine functions http://code.google.com/p/lilypond/issues/detail?id=1518 (No comment was entered for this change.) ___

Re: Issue 748 in lilypond: Modes should support quarter-tones

Updates: Status: Verified Comment #9 on issue 748 by colinpkc...@gmail.com: Modes should support quarter-tones http://code.google.com/p/lilypond/issues/detail?id=748 (No comment was entered for this change.) ___ bug-lilypond mailing list b

Re: Issue 649 in lilypond: Let accidentals on tied notes across a break not be valid for subsequent notes

Updates: Summary: Let accidentals on tied notes across a break not be valid for subsequent notes Status: Accepted Labels: -Type-Defect Type-Enhancement Comment #7 on issue 649 by percival.music.ca: Let accidentals on tied notes across a break not be valid for subsequent note

Re: Unnecessary accidental after tied note at the beginning of a new system

Hello, -Original Message- From: Keith OHara Date: Mon, 7 Mar 2011 04:03:24 + To: bug-lilypond Subject: Re: Unnecessary accidental after tied note at the beginning of a new system >Neil Puttock gmail.com> writes: >>On 6 March 2011 16:34, Zoltan Selyem elte.hu> wrote: >>> >>> % Hell

Re: Issue 1488 in lilypond: [PATCH]harmonics and slides (issue3590041)

Updates: Status: Verified Comment #11 on issue 1488 by percival.music.ca: [PATCH]harmonics and slides (issue3590041) http://code.google.com/p/lilypond/issues/detail?id=1488 @Neil: done, thanks. @Phil: the doc patch from Patrick Schmidt contains a small amount of new code (in ly/cho