Another cross-staff beaming problem?

2011-05-03 Thread Phil Holmes
I can't find a bug report that covers this issue. It was introduced between 13.51 and 13.52 and gives faulty beaming when using manual cross-staff beams. It remains in 13.61. Here's an example cut down from my initial 20 voice 500 bar sample that shows it - but it's not quite tiny. Could

Re: Another cross-staff beaming problem?

2011-05-03 Thread Colin Campbell
On 11-05-03 02:14 AM, Phil Holmes wrote: I can't find a bug report that covers this issue. It was introduced between 13.51 and 13.52 and gives faulty beaming when using manual cross-staff beams. It remains in 13.61. Here's an example cut down from my initial 20 voice 500 bar sample that

Re: Another cross-staff beaming problem?

2011-05-03 Thread Phil Holmes
Colin Campbell c...@shaw.ca wrote in message news:4dbffdfe.7090...@shaw.ca... On 11-05-03 02:14 AM, Phil Holmes wrote: I can't find a bug report that covers this issue. It was introduced between 13.51 and 13.52 and gives faulty beaming when using manual cross-staff beams. It remains in

Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice

2011-05-03 Thread lilypond
Comment #9 on issue 1613 by m...@apollinemike.com: Beamed stems too long when avoiding low note in other voice http://code.google.com/p/lilypond/issues/detail?id=1613 http://codereview.appspot.com/4426072/ This patch fits with option #2 as described above (build a list of intervals to

Re: Another cross-staff beaming problem?

2011-05-03 Thread Keith OHara
Phil Holmes mail at philholmes.net writes: Could you check it with 13.60 or .61 to confirm it was wrong in a previous version? If it was, I assume it was a bug but that it's fixed in a development version. Phil, Confirming that your example comes out wrong with 2.13.61 as released. It

Re: Issue 1641 in lilypond: noBeam disables beaming of prior notes

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #2 on issue 1641 by colinpkc...@gmail.com: noBeam disables beaming of prior notes http://code.google.com/p/lilypond/issues/detail?id=1641 Verified 2.15.0 ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #6 on issue 1622 by colinpkc...@gmail.com: Dynamic spanner not printed within grace notes http://code.google.com/p/lilypond/issues/detail?id=1622 Verified 2.15.0 ___ bug-lilypond mailing list

Re: Issue 1632 in lilypond: beam staff change weird angular beam

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #5 on issue 1632 by colinpkc...@gmail.com: beam staff change weird angular beam http://code.google.com/p/lilypond/issues/detail?id=1632 Verified 2.15.0 ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1612 in lilypond: Change staff produces long stems

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #24 on issue 1612 by colinpkc...@gmail.com: Change staff produces long stems http://code.google.com/p/lilypond/issues/detail?id=1612 Verified 2.15.0 (the original report) ___ bug-lilypond mailing list

Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #23 on issue 1555 by colinpkc...@gmail.com: Multiple warnings concerning staff-affinities http://code.google.com/p/lilypond/issues/detail?id=1555 Verified 2.15.0 only one warning is produced. ___

Re: Issue 1547 in lilypond: Too many colliding rests

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #4 on issue 1547 by colinpkc...@gmail.com: Too many colliding rests http://code.google.com/p/lilypond/issues/detail?id=1547 Verified 2.15.0 ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #5 on issue 1502 by colinpkc...@gmail.com: DOcument information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 Verified 2.15.0 ___

Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes

2011-05-03 Thread Keith OHara
lilypond at googlecode.com writes: Updates: Status: Verified Comment #6 on issue 1622 by colinpkc...@gmail.com: Dynamic spanner not printed within grace notes http://code.google.com/p/lilypond/issues/detail?id=1622 Verified 2.15.0 But 2.15.0 has not been released yet,

Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #6 on issue 1626 by colinpkc...@gmail.com: Articulate produces faulty barcheck warnings http://code.google.com/p/lilypond/issues/detail?id=1626 Verified 2.15.0 ___ bug-lilypond mailing list

Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #13 on issue 1633 by colinpkc...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Verified 2.15.0 ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1574 in lilypond: DOC: Need updated/expanded documentation of percent repeat/beat slash

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #4 on issue 1574 by colinpkc...@gmail.com: DOC: Need updated/expanded documentation of percent repeat/beat slash http://code.google.com/p/lilypond/issues/detail?id=1574 Verified 2.15.0 ___ bug-lilypond

Re: Issue 1616 in lilypond: old website link gives false doc suggestion info

2011-05-03 Thread lilypond
Updates: Status: Verified Comment #2 on issue 1616 by colinpkc...@gmail.com: old website link gives false doc suggestion info http://code.google.com/p/lilypond/issues/detail?id=1616 Verified 2.15.0 ___ bug-lilypond mailing list

Re: Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong

2011-05-03 Thread lilypond
Updates: Labels: fixed_2_15_0 Comment #4 on issue 1614 by n.putt...@gmail.com: DynamicTextSpanner documentation is wrong http://code.google.com/p/lilypond/issues/detail?id=1614 but the docs need updating in git See commit f3a35eaef2b78440cdb150d36d8ff6d93e9c8d46.