Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes
On 11-05-03 01:01 PM, Keith OHara wrote: 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, Colin. Another change between now and the release might destroy the fix (which has happened when a fix caused a worse problem an had to be taken back) or the fix might not appear in the released build for which it was intended (which has also happened recently). I am rubbish at understanding policy documents (and following instructions in general) but I think the CG intends that we test only the released builds when it says 'official GUB version'. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond Actually, 2.15.0 _is_ the version reported by the gub I built yesterday, Keith: colin@Sherlock:~$ which lilypond /home/colin/bin/lilypond colin@Sherlock:~$ lilypond -v GNU LilyPond 2.15.0 Colin -- The test of our progress is not whether we add more to the abundance of those who have much, it is whether we provide enough for those who have too little. -Franklin D. Roosevelt, 32nd US President (1882-1945) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong
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. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1616 in lilypond: old website link gives false doc suggestion info
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 bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong
Comment #3 on issue 1614 by colinpkc...@gmail.com: DynamicTextSpanner documentation is wrong http://code.google.com/p/lilypond/issues/detail?id=1614 The original in LSR is corrected, but the docs need updating in git. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1574 in lilypond: DOC: Need updated/expanded documentation of percent repeat/beat slash
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 mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
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 https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings
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 bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes
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, Colin. Another change between now and the release might destroy the fix (which has happened when a fix caused a worse problem an had to be taken back) or the fix might not appear in the released build for which it was intended (which has also happened recently). I am rubbish at understanding policy documents (and following instructions in general) but I think the CG intends that we test only the released builds when it says 'official GUB version'. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters
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 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1547 in lilypond: Too many colliding rests
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 https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities
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. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1612 in lilypond: Change staff produces long stems
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 bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1632 in lilypond: beam staff change weird angular beam
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 https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes
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 bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1641 in lilypond: noBeam disables beaming of prior notes
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 https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Another cross-staff beaming problem?
Phil Holmes 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 starts coming out right with the patch that fixes issue 1632, so we can consider this the same bug as 1632. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice
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 describe where a beam may not go, then thread the beam between those intervals), and I believe it works. The problem with making collision-voice-only the default is that it seems not to be that which a user would expect from automated engraving - I think that most people will want automatic collision avoidance (albeit non-buggy automatic avoidance, which I think the patch on issue 4426072 offers). ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Another cross-staff beaming problem?
"Colin Campbell" 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 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 someone confirm it's new? I've just run your example through 2.12.3, 2.15.0 and 2.13.62, (all using Frescobaldi's great multiple version feature) and all three versions seemed correct, in that they matched your CrossStaffBugRight image. cheers, Colin 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 Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Another cross-staff beaming problem?
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 shows it - but it's not quite tiny. Could someone confirm it's new? I've just run your example through 2.12.3, 2.15.0 and 2.13.62, (all using Frescobaldi's great multiple version feature) and all three versions seemed correct, in that they matched your CrossStaffBugRight image. cheers, Colin -- The test of our progress is not whether we add more to the abundance of those who have much, it is whether we provide enough for those who have too little. -Franklin D. Roosevelt, 32nd US President (1882-1945) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Another cross-staff beaming problem?
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 someone
confirm it's new?
{
<<
\new PianoStaff <<
\new Staff = "up"
<<
\new Voice {
\clef "treble"
\key bes\major
\time 2/4
\voiceOne < d' bes'>8 [ f'8 ] \oneVoice r8 \voiceOne f'8 \bar "|."
}
\new Voice {
\clef "treble"
\key bes\major
\time 2/4
\voiceTwo s8 f'8 [ \voiceOne \change Staff = "down" f8 \voiceTwo
\change Staff = "up" f'8 ] \bar "|."
}
\new Staff = "down"
<<
\new Voice {
\clef "bass"
\key bes\major
\time 2/4
< bes,, bes,>8 r8 \voiceTwo f8 \oneVoice r8 \bar "|."
}
}
--
Phil Holmes
Bug Squad
<><>___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
