Re: Issue 1986 in lilypond: Patch: Fixes slope errors from incorrect X extents in Beam::print.

2011-10-25 Thread lilypond
Updates: Labels: Patch-new Comment #4 on issue 1986 by mts...@gmail.com: Patch: Fixes slope errors from incorrect X extents in Beam::print. http://code.google.com/p/lilypond/issues/detail?id=1986#c4 Fixes slope errors from incorrect X extents in Beam::print.

Re: \override Beam #'consistent-slope = ##t should be default

2011-10-25 Thread mike
On Oct 25, 2011, at 5:32 AM, Keith OHara wrote: There are lots of broken beams in Scriabin's first prelude http://imslp.org/wiki/24_Preludes,_Op.11_(Scriabin,_Aleksandr) The original publisher makes no attempt at consistent slopes. Peters Edition prints nearly-equal slopes across the

Re: \override Beam #'consistent-slope = ##t should be default

2011-10-25 Thread m...@apollinemike.com
errata: more note flat = more not flat On Oct 25, 2011, at 10:06 AM, m...@apollinemike.com wrote: On Oct 25, 2011, at 5:32 AM, Keith OHara wrote: There are lots of broken beams in Scriabin's first prelude http://imslp.org/wiki/24_Preludes,_Op.11_(Scriabin,_Aleksandr) The original publisher

Re: \override Beam #'consistent-slope = ##t should be default

2011-10-25 Thread David Kastrup
m...@apollinemike.com writes: 3) Aside from what I mention in (2), are there any other criteria that, in your opinion, seem to govern slope breaking? Could these criteria vary from work to work, edition to edition, style to style? Does Elaine Gould have anything to say on the subject? I can

Patch-needs_work vs. others

2011-10-25 Thread Graham Percival
On Tue, Oct 25, 2011 at 10:08:34AM +, lilyp...@googlecode.com wrote: I think that Needs-evidence is sufficient for indicating the need for discussion. The patch status would remain Patch-review (meaning that the patch may or may not be acceptable in his current form but is not going

Re: Issue 1663 in lilypond: Images missing on web site

2011-10-25 Thread lilypond
Comment #55 on issue 1663 by percival.music...@gmail.com: Images missing on web site http://code.google.com/p/lilypond/issues/detail?id=1663 Thanks, I've changed Patchy to use git apply instead of patch(1).

Re: Patch-needs_work vs. others

2011-10-25 Thread David Kastrup
Graham Percival gra...@percival-music.ca writes: On Tue, Oct 25, 2011 at 10:08:34AM +, lilyp...@googlecode.com wrote: I think that Needs-evidence is sufficient for indicating the need for discussion. The patch status would remain Patch-review (meaning that the patch may or may not be

Re: Patch-needs_work vs. others

2011-10-25 Thread Graham Percival
On Tue, Oct 25, 2011 at 01:20:33PM +0200, David Kastrup wrote: Graham Percival gra...@percival-music.ca writes: convenient). It should only contain patches that have completed a countdown, and/or patches that the author wishes to skip the review process. Shrug. That means to me that

Issue 1992 in lilypond: Patch: Fixes all duplicate declarations of Flag #'transparent

2011-10-25 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1992 by mts...@gmail.com: Patch: Fixes all duplicate declarations of Flag #'transparent http://code.google.com/p/lilypond/issues/detail?id=1992 Fixes all duplicate declarations of Flag #'transparent

Re: Issue 1987 in lilypond: Patch: Get rid of most of the insane string-tunings API

2011-10-25 Thread lilypond
Updates: Labels: Patch-new Comment #10 on issue 1987 by d...@gnu.org: Patch: Get rid of most of the insane string-tunings API http://code.google.com/p/lilypond/issues/detail?id=1987#c10 Get rid of most of the insane string-tunings API convert-ly rules are there. Translations should

Re: Issue 1987 in lilypond: Patch: Get rid of most of the insane string-tunings API

2011-10-25 Thread lilypond
Updates: Owner: d...@gnu.org Cc: carl.d.s...@gmail.com Comment #11 on issue 1987 by d...@gnu.org: Patch: Get rid of most of the insane string-tunings API http://code.google.com/p/lilypond/issues/detail?id=1987 Regarding comment #10: it is totally annoying that git cl upload,

Re: Issue 1984 in lilypond: Patch: parser.yy: make Scheme and music expressions equivalent as function arguments.

2011-10-25 Thread lilypond
Updates: Status: Fixed Labels: -Patch-countdown Comment #5 on issue 1984 by d...@gnu.org: Patch: parser.yy: make Scheme and music expressions equivalent as function arguments. http://code.google.com/p/lilypond/issues/detail?id=1984 Pushed as

Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs

2011-10-25 Thread lilypond
Comment #6 on issue 1943 by stans...@gmail.com: lilypond after 2.15.8 fails on x86 Macs http://code.google.com/p/lilypond/issues/detail?id=1943 lilypond-2.15.15-1.darwin-x86.tar.bz2 also crashes following expansion on my iMac. Once again, Get Info about the expanded file incorrectly

Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs

2011-10-25 Thread lilypond
Comment #7 on issue 1943 by chh...@gmail.com: lilypond after 2.15.8 fails on x86 Macs http://code.google.com/p/lilypond/issues/detail?id=1943 For this next try I have used the official Python distribution form Mac (fat i386/PPC) from python.org. I tested the x86 version on 10.7. I'd like

Re: Issue 1567 in lilypond: Add documentation for footnotes

2011-10-25 Thread lilypond
Updates: Labels: -Priority-Medium Patch-review Comment #14 on issue 1567 by pkx1...@gmail.com: Add documentation for footnotes http://code.google.com/p/lilypond/issues/detail?id=1567 Patch ready for review. Passes make and a full make doc http://codereview.appspot.com/5315053/

Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs

2011-10-25 Thread lilypond
Comment #8 on issue 1943 by stans...@gmail.com: lilypond after 2.15.8 fails on x86 Macs http://code.google.com/p/lilypond/issues/detail?id=1943 On iMac running OS 10.5.8 it failed, this time with a dialog box saying LilyPond Error and giving me the choice of going to Console or

Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs

2011-10-25 Thread lilypond
Comment #9 on issue 1943 by stans...@gmail.com: lilypond after 2.15.8 fails on x86 Macs http://code.google.com/p/lilypond/issues/detail?id=1943 Re: ppc version. On PowerBook G4, OS 10.5.8, the http://klarinett.li/lilypond/lilypond-2.15.15-darwin-ppc.tar.bz2 also failed with the LilyPond

Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs

2011-10-25 Thread lilypond
Comment #10 on issue 1943 by stans...@gmail.com: lilypond after 2.15.8 fails on x86 Macs http://code.google.com/p/lilypond/issues/detail?id=1943 Please note that the official ppc version 2.15.15-1 for PPC (downloaded from the LilyPond.org site) appears to be working normally. I converted

Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs

2011-10-25 Thread lilypond
Comment #11 on issue 1943 by chh...@gmail.com: lilypond after 2.15.8 fails on x86 Macs http://code.google.com/p/lilypond/issues/detail?id=1943 The official PPC binary still uses the previous LilyPond.app. For the x86 version this was changed to support 10.7. Do any, or both of the

Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs

2011-10-25 Thread lilypond
Comment #12 on issue 1943 by stans...@gmail.com: lilypond after 2.15.8 fails on x86 Macs http://code.google.com/p/lilypond/issues/detail?id=1943 On PPC OS 10.5.8, by moving missing files from 2.15.14-1 (official download) into Resources, both of the above bundles appear to work. On x86

Re: Issue 1988 in lilypond: Patch: Rename \markuplines to \markuplist (before running convert-ly)

2011-10-25 Thread lilypond
Updates: Labels: Patch-review Comment #8 on issue 1988 by percival.music...@gmail.com: Patch: Rename \markuplines to \markuplist (before running convert-ly) http://code.google.com/p/lilypond/issues/detail?id=1988#c8 Patchy the autobot says: LGTM.

Re: Issue 1992 in lilypond: Patch: Fixes all duplicate declarations of Flag #'transparent

2011-10-25 Thread lilypond
Updates: Labels: Patch-review Comment #1 on issue 1992 by percival.music...@gmail.com: Patch: Fixes all duplicate declarations of Flag #'transparent http://code.google.com/p/lilypond/issues/detail?id=1992#c1 Patchy the autobot says: LGTM.

Re: Issue 1567 in lilypond: Add documentation for footnotes

2011-10-25 Thread lilypond
Updates: Labels: -Patch-review Patch-needs_work Comment #15 on issue 1567 by colinpkc...@gmail.com: Add documentation for footnotes http://code.google.com/p/lilypond/issues/detail?id=1567 Mike has comments on Rietveld. ___ bug-lilypond

Re: Issue 1988 in lilypond: Patch: Rename \markuplines to \markuplist (before running convert-ly)

2011-10-25 Thread lilypond
Updates: Labels: -Patch-review Patch-countdown Comment #9 on issue 1988 by colinpkc...@gmail.com: Patch: Rename \markuplines to \markuplist (before running convert-ly) http://code.google.com/p/lilypond/issues/detail?id=1988 (No comment was entered for this change.)

Re: Issue 1127 in lilypond: Piano staff centred dynamics

2011-10-25 Thread lilypond
Comment #8 on issue 1127 by k-ohara5...@oco.net: Piano staff centred dynamics http://code.google.com/p/lilypond/issues/detail?id=1127 So it seems the desire is to move individual dynamics (or groups linked as per issue 1362). When the music is tight the dynamics are forced midway