Re: Issue 664 in lilypond: 1 breakable glissando = 2 same-looking glissandos

2011-08-18 Thread lilypond
Updates: Status: Fixed Comment #1 on issue 664 by mts...@gmail.com: 1 breakable glissando = 2 same-looking glissandos http://code.google.com/p/lilypond/issues/detail?id=664 (No comment was entered for this change.) ___ bug-lilypond

Re: Issue 827 in lilypond: Tuplet brackets should be continued after a line break

2011-08-18 Thread lilypond
Comment #2 on issue 827 by mts...@gmail.com: Tuplet brackets should be continued after a line break http://code.google.com/p/lilypond/issues/detail?id=827 What would the desirable output be here? I'd say nix the tuplet number on the second tuplet and the tuplet bracket on the first.

Re: Issue 723 in lilypond: wrong horizontal alignement of pedal brackets with a second inside a chord

2011-08-18 Thread lilypond
Updates: Labels: Patch-new Patch-review Comment #1 on issue 723 by mts...@gmail.com: wrong horizontal alignement of pedal brackets with a second inside a chord http://code.google.com/p/lilypond/issues/detail?id=723 http://codereview.appspot.com/4899050

Re: Issue 1756 in lilypond: architecture diagram image is missing

2011-08-18 Thread lilypond
Updates: Status: Fixed Comment #7 on issue 1756 by philehol...@googlemail.com: architecture diagram image is missing http://code.google.com/p/lilypond/issues/detail?id=1756 Pushed with commit: 9a0680df4d6b24876c54981e25cab02aceac3d53 ___

Re: Issue 1813 in lilypond: Doc: Overlapping boxes and section headers in LM

2011-08-18 Thread lilypond
Updates: Status: Fixed Labels: -Frog fixed_2_15_9 Comment #5 on issue 1813 by philehol...@googlemail.com: Doc: Overlapping boxes and section headers in LM http://code.google.com/p/lilypond/issues/detail?id=1813 Pushed as f9b28c30a3badc92aaacbb70c56e5114fc1d77ab

convert-ly myfile.ly mynewfile.ly

2011-08-18 Thread Patrick Schmidt
Hi all, by accident I noticed that when you try to upgrade a file (to version 2.14.2) that is already up to date (2.14.0) with convert-ly myfile.ly mynewfile.ly a new but empty file is created. There aren't any error messages. When you fake an older version number everything works out and a

Re: Issue 827 in lilypond: Tuplet brackets should be continued after a line break

2011-08-18 Thread lilypond
Comment #3 on issue 827 by trevorb...@gmail.com: Tuplet brackets should be continued after a line break http://code.google.com/p/lilypond/issues/detail?id=827 I would imagine that the formatting should be the same for both the left and right halves of the broken tuplet. So I would say

Re: Issue 982 in lilypond: web big-html and pdf look bad

2011-08-18 Thread lilypond
Comment #5 on issue 982 by philehol...@googlemail.com: web big-html and pdf look bad http://code.google.com/p/lilypond/issues/detail?id=982 I did an infeasible amount of work comparing different approaches to getting an optimum image. I concluded that making texi2pdf force the images to

Re: Issue 153 in lilypond: \once \set fails to restore previous setting

2011-08-18 Thread lilypond
Updates: Status: Verified Comment #19 on issue 153 by philehol...@googlemail.com: \once \set fails to restore previous setting http://code.google.com/p/lilypond/issues/detail?id=153 (No comment was entered for this change.) ___

Re: Issue 1762 in lilypond: mutual cues fail

2011-08-18 Thread lilypond
Updates: Status: Verified Comment #7 on issue 1762 by philehol...@googlemail.com: mutual cues fail http://code.google.com/p/lilypond/issues/detail?id=1762 (No comment was entered for this change.) ___ bug-lilypond mailing list

Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests.

2011-08-18 Thread lilypond
Updates: Status: Verified Comment #6 on issue 1720 by philehol...@googlemail.com: Incorrect tuplet bracket direction calculation when tuplets contain rests. http://code.google.com/p/lilypond/issues/detail?id=1720 (No comment was entered for this change.)

Re: Issue 1390 in lilypond: Tied acciaccaturas should not be printed with a slur

2011-08-18 Thread lilypond
Comment #13 on issue 1390 by philehol...@googlemail.com: Tied acciaccaturas should not be printed with a slur http://code.google.com/p/lilypond/issues/detail?id=1390 Not sure of the process here. I really think this change would benefit by being added to the Grace notes section of the NR

Re: convert-ly myfile.ly mynewfile.ly

2011-08-18 Thread Dmytro O. Redchuk
On Wed 17 Aug 2011, 19:43 Patrick Schmidt wrote: Hi all, by accident I noticed that when you try to upgrade a file (to version 2.14.2) that is already up to date (2.14.0) with convert-ly myfile.ly mynewfile.ly a new but empty file is created. There aren't any error messages. When you

Re: Issue 1099 in lilypond: flat collides with stem in some cases

2011-08-18 Thread lilypond
Updates: Status: Verified Mergedinto: Comment #2 on issue 1099 by philehol...@googlemail.com: flat collides with stem in some cases http://code.google.com/p/lilypond/issues/detail?id=1099 (No comment was entered for this change.)

Issue 1825 in lilypond: convert-ly produces no output having run on up-to-date source

2011-08-18 Thread lilypond
Status: Accepted Owner: Labels: Type-Scripts Priority-Medium New issue 1825 by brownian.box: convert-ly produces no output having run on up-to-date source http://code.google.com/p/lilypond/issues/detail?id=1825 Reported by Patrick Schmidt,

Re: Issue 1006 in lilypond: Breathing sign collides with flat

2011-08-18 Thread lilypond
Updates: Status: Verified Comment #4 on issue 1006 by philehol...@googlemail.com: Breathing sign collides with flat http://code.google.com/p/lilypond/issues/detail?id=1006 Fixed between 13.49 and 13.51, FWIW. ___ bug-lilypond mailing list

Re: Issue 690 in lilypond: Beams and stems disappear when using RemoveEmpltyStaffContext in a PianoStaff

2011-08-18 Thread lilypond
Updates: Status: Verified Comment #4 on issue 690 by philehol...@googlemail.com: Beams and stems disappear when using RemoveEmpltyStaffContext in a PianoStaff http://code.google.com/p/lilypond/issues/detail?id=690 (No comment was entered for this change.)

Re: Issue 664 in lilypond: 1 breakable glissando = 2 same-looking glissandos

2011-08-18 Thread lilypond
Updates: Status: Verified Comment #2 on issue 664 by philehol...@googlemail.com: 1 breakable glissando = 2 same-looking glissandos http://code.google.com/p/lilypond/issues/detail?id=664 (No comment was entered for this change.) Attachments: 664.png 2.8 KB

Re: Issue 631 in lilypond: Dynamics collide with cross-staff barlines when attached to skips

2011-08-18 Thread lilypond
Comment #8 on issue 631 by philehol...@googlemail.com: Dynamics collide with cross-staff barlines when attached to skips http://code.google.com/p/lilypond/issues/detail?id=631 Keith - are you claiming this in 2.15.9? ___ bug-lilypond mailing list

Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds.

2011-08-18 Thread lilypond
Comment #12 on issue 620 by philehol...@googlemail.com: It should be possible to specify more specific spanner bounds. http://code.google.com/p/lilypond/issues/detail?id=620 Ditto - this is 2.15.9, right? ___ bug-lilypond mailing list

Re: Issue 592 in lilypond: Regression: Tie direction reverse incorrectly on a middle-staff note

2011-08-18 Thread lilypond
Updates: Status: Verified Comment #5 on issue 592 by philehol...@googlemail.com: Regression: Tie direction reverse incorrectly on a middle-staff note http://code.google.com/p/lilypond/issues/detail?id=592 (No comment was entered for this change.)

Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used.

2011-08-18 Thread lilypond
Updates: Owner: ianhuli...@gmail.com Comment #21 on issue 1349 by pnorcks: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used. http://code.google.com/p/lilypond/issues/detail?id=1349 Ian is handling this issue.

Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated

2011-08-18 Thread lilypond
Status: Accepted Owner: New issue 1826 by pnorcks: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated http://code.google.com/p/lilypond/issues/detail?id=1826 When compiling LilyPond against the Guile 2.0.2 library (after applying Ian's patch from issue

Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated

2011-08-18 Thread lilypond
Comment #1 on issue 1826 by pnorcks: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated http://code.google.com/p/lilypond/issues/detail?id=1826 One possible patch is attached. Attachments: conditional-circle.patch 1.3 KB

Re: Issue 1422 in lilypond: Beam edges over rests should not be centered

2011-08-18 Thread lilypond
Comment #2 on issue 1422 by mts...@gmail.com: Beam edges over rests should not be centered http://code.google.com/p/lilypond/issues/detail?id=1422 I agree - I think the issue should be closed, especially as stemlets would need to descend down to the center of the rest.

Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated

2011-08-18 Thread lilypond
Comment #2 on issue 1826 by reinhold...@gmail.com: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated http://code.google.com/p/lilypond/issues/detail?id=1826 That's such a specialized markup (checking for trigger=0.5, which doesn't make sense anywhere else) that

Re: Issue 1808 in lilypond: [PATCH] Implement MusicXML files in lilypond-book

2011-08-18 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review fixed_2_15_9 Comment #2 on issue 1808 by reinhold...@gmail.com: [PATCH] Implement MusicXML files in lilypond-book http://code.google.com/p/lilypond/issues/detail?id=1808 Pushed as commit 55cdf3441eca8d6489c486767cf8013b08e8b32e

Re: Issue 631 in lilypond: Dynamics collide with cross-staff barlines when attached to skips

2011-08-18 Thread lilypond
Comment #9 on issue 631 by k-ohara5...@oco.net: Dynamics collide with cross-staff barlines when attached to skips http://code.google.com/p/lilypond/issues/detail?id=631 claiming this in 2.15.9? No. We rejected the proposed fix, for reasons listed under issue 621. I am claiming that this

Re: Issue 1422 in lilypond: Beam edges over rests should not be centered

2011-08-18 Thread lilypond
Updates: Status: Invalid Comment #3 on issue 1422 by k-ohara5...@oco.net: Beam edges over rests should not be centered http://code.google.com/p/lilypond/issues/detail?id=1422 Seconding the motion to close, with an image showing why the current beam endings are correct. Any opposed

Re: Issue 723 in lilypond: wrong horizontal alignement of pedal brackets with a second inside a chord

2011-08-18 Thread lilypond
Updates: Labels: -Patch-new -Patch-review Patch-needs_work Comment #2 on issue 723 by k-ohara5...@oco.net: wrong horizontal alignement of pedal brackets with a second inside a chord http://code.google.com/p/lilypond/issues/detail?id=723 The patch of comment 1 gives the attached,