Re: Issue 1440 in lilypond: \book(part) containing page-marker as only element segfaults

2010-12-07 Thread lilypond
Comment #1 on issue 1440 by n.puttock: \book(part) containing page-marker as only element segfaults http://code.google.com/p/lilypond/issues/detail?id=1440 The following patch seems to work: diff --git a/lily/constrained-breaking.cc b/lily/constrained-breaking.cc index 29c00e1..a2f61ef 10064

Issue 1440 in lilypond: \book(part) containing page-marker as only element segfaults

2010-12-07 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Critical New issue 1440 by n.puttock: \book(part) containing page-marker as only element segfaults http://code.google.com/p/lilypond/issues/detail?id=1440 \version "2.13.42" \book { \label #'foo } Program received signal SIGSEGV, Seg

Re: Issue 1427 in lilypond: \bookpart stored in a variable can't contain markup

2010-12-07 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_13_42 Comment #8 on issue 1427 by n.puttock: \bookpart stored in a variable can't contain markup http://code.google.com/p/lilypond/issues/detail?id=1427 but the example in comment #1 still segfaults I'll post a new issue for this once

Issue 1439 in lilypond: dashes in barline and spanbar should be the same

2010-12-07 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Low New issue 1439 by brownian.box: dashes in barline and spanbar should be the same http://code.google.com/p/lilypond/issues/detail?id=1439 \version "2.13.41" \score { \new ChoirStaff << \new Staff { c''1 \bar "dashed" c''1 }

Re: Issue 1434 in lilypond: SVG backend: xml:space="preserve" is needed for and/or

2010-12-07 Thread lilypond
Comment #9 on issue 1434 by pnorcks: SVG backend: xml:space="preserve" is needed for and/or http://code.google.com/p/lilypond/issues/detail?id=1434 Yes, the "preserve" attribute works correctly everywhere else I've checked: Chromium, Firefox, Inkscape, Opera, Batik Squiggle, etc. _

Re: figured-bass-extenders-markup.ly

2010-12-07 Thread Phil Holmes
"Phil Holmes" wrote in message news:idj11j$8r...@dough.gmane.org... The attached file is a "before and after" of figured-bass-extenders-markup.ly showing the difference between 13.40 and 13.41. I don't know why there is any difference. Can someone shed any light, or is it a bug? http://code.

Issue 1438 in lilypond: Change to figured-bass-extenders-markup.ly regtest

2010-12-07 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-High Regression New issue 1438 by PhilEHolmes: Change to figured-bass-extenders-markup.ly regtest http://code.google.com/p/lilypond/issues/detail?id=1438 The attached file shows a significant difference in a regtest between versions

Re: Issue 1411 in lilypond: Piano phrasing slur collision with lyrics

2010-12-07 Thread lilypond
Updates: Labels: -Priority-Low Priority-Medium Comment #2 on issue 1411 by v.villenave: Piano phrasing slur collision with lyrics http://code.google.com/p/lilypond/issues/detail?id=1411 There you go. Attachments: ex.preview.png 6.7 KB __

Re: Issue 1426 in lilypond: [PATCH]Better support for beat slashes (multi-slash & mixed duration). (issue212048)

2010-12-07 Thread lilypond
Updates: Owner: n.puttock Labels: Priority-Medium Type-Enhancement Comment #1 on issue 1426 by percival.music.ca: [PATCH]Better support for beat slashes (multi-slash & mixed duration). (issue212048) http://code.google.com/p/lilypond/issues/detail?id=1426 (No comment was entere

Re: Issue 1381 in lilypond: Add documentation for text dynamic spanners like \cresc

2010-12-07 Thread lilypond
Updates: Labels: Priority-Medium Comment #1 on issue 1381 by percival.music.ca: Add documentation for text dynamic spanners like \cresc http://code.google.com/p/lilypond/issues/detail?id=1381 (No comment was entered for this change.) ___ b

Re: Issue 1379 in lilypond: augmentum in Gregorian notation compromises layout and is applied to wrong (groups of) notes

2010-12-07 Thread lilypond
Updates: Labels: Priority-Postponed Comment #1 on issue 1379 by percival.music.ca: augmentum in Gregorian notation compromises layout and is applied to wrong (groups of) notes http://code.google.com/p/lilypond/issues/detail?id=1379 (No comment was entered for this change.) _

Re: Issue 1411 in lilypond: Piano phrasing slur collision with lyrics

2010-12-07 Thread lilypond
Updates: Labels: Priority-Low Comment #1 on issue 1411 by percival.music.ca: Piano phrasing slur collision with lyrics http://code.google.com/p/lilypond/issues/detail?id=1411 I'm missing a png file, so I'll just guess a priority. ___ bug-l

Re: Issue 1378 in lilypond: gregorian notation: collision with finalis.

2010-12-07 Thread lilypond
Updates: Labels: Priority-Postponed Comment #1 on issue 1378 by percival.music.ca: gregorian notation: collision with finalis. http://code.google.com/p/lilypond/issues/detail?id=1378 Postponed because nobody is working on ancient music. __

Re: Issue 1368 in lilypond: ly:score-set-header! badly documented

2010-12-07 Thread lilypond
Updates: Labels: Priority-Low Comment #1 on issue 1368 by percival.music.ca: ly:score-set-header! badly documented http://code.google.com/p/lilypond/issues/detail?id=1368 (No comment was entered for this change.) ___ bug-lilypond mailing l

Re: Issue 1427 in lilypond: \bookpart stored in a variable can't contain markup

2010-12-07 Thread lilypond
Comment #7 on issue 1427 by percival.music.ca: \bookpart stored in a variable can't contain markup http://code.google.com/p/lilypond/issues/detail?id=1427 After applying http://codereview.appspot.com/3319041/ the example in comment #0 compiles fine, but the example in comment #1 still seg

Re: Issue 1434 in lilypond: SVG backend: xml:space="preserve" is needed for and/or

2010-12-07 Thread lilypond
Comment #8 on issue 1434 by v.villenave: SVG backend: xml:space="preserve" is needed for and/or http://code.google.com/p/lilypond/issues/detail?id=1434 Wow, I can't believe you even sent them a patch! :-) What about other SVG rendering engines? Does the "preserve" attribute work appropri

Re: DynamicText + SpanBar collision; #'spanbar-padding ?

2010-12-07 Thread Trevor Daniels
Mark Polesky wrote Tuesday, December 07, 2010 8:03 AM The \ppp collides with the SpanBar in the example below. \new StaffGroup \relative f' << \new Staff { R1 | f2\ppp r | } \new Staff { R1 | f1 | } could someone at least recommend a workaround to get the dynamics+notes to move to the

DynamicText + SpanBar collision; #'spanbar-padding ?

2010-12-07 Thread Mark Polesky
The \ppp collides with the SpanBar in the example below. \new StaffGroup \relative f' << \new Staff { R1 | f2\ppp r | } \new Staff { R1 | f1 | } >> Strangely, it seems that none of my three notation manuals specifically address this (Ross, Stone, Read). Of course, I have seen cases in publis