Re: Issue 1843 in lilypond: Creates a Flag grob

2011-09-11 Thread lilypond
Comment #3 on issue 1843 by x.sche...@gmail.com: Creates a Flag grob http://code.google.com/p/lilypond/issues/detail?id=1843 Could you check there is a convert-ly rule for this? And add it if needed? :-) ___ bug-lilypond mailing list bug-lilypond@gn

Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem

2011-09-11 Thread lilypond
Comment #1 on issue 1881 by n.putt...@gmail.com: Multiple cyclic dependency errors for Beam/Stem http://code.google.com/p/lilypond/issues/detail?id=1881 Here's a diff from make check for autobeam-show-defaults.ly. It changes for each test, so always shows up (and it's one of many). Attac

Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem

2011-09-11 Thread lilypond
Status: Accepted Owner: Labels: Type-Critical New issue 1881 by n.putt...@gmail.com: Multiple cyclic dependency errors for Beam/Stem http://code.google.com/p/lilypond/issues/detail?id=1881 Following commit 6465274e66a851cccd4cd32a521abc853f3e79dd, `Restores stem length and stem-begin-p

Re: Zeichenkodierung für Lilypond

2011-09-11 Thread Urs Liska
More details, more concrete please! Am 11.09.2011 22:56, schrieb Thomas: Hallo, welche zeichenkodierung benutzt ihr für Lilipond? Ich kanns nicht lesen. Mit UTF-8 geht es nicht. Danke Thomas ___ bug-lilypond mailing list bug-lilypond@gnu.org https

Zeichenkodierung für Lilypond

2011-09-11 Thread Thomas
Hallo, welche zeichenkodierung benutzt ihr für Lilipond? Ich kanns nicht lesen. Mit UTF-8 geht es nicht. Danke Thomas ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2

2011-09-11 Thread lilypond
Updates: Labels: -Patch-review Patch-needs_work Comment #16 on issue 1780 by pkx1...@gmail.com: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2 http://code.google.com/p/lilypond/issues/detail?id=1780 (No comment was entered for this change.

Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string

2011-09-11 Thread lilypond
Updates: Status: Fixed Labels: -Patch-push Comment #14 on issue 1741 by d...@gnu.org: Tablature Bug when pitch is higher then beh in a quarter-tone string http://code.google.com/p/lilypond/issues/detail?id=1741 Pushed as 5f1308c20d09eb5385f746e7ee05932ae079b5a6 Note that this

Re: Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly

2011-09-11 Thread lilypond
Updates: Status: Fixed Owner: tdaniels...@googlemail.com Labels: fixed_2_15_11 Comment #2 on issue 1880 by tdaniels...@googlemail.com: Presence of a bar number changes whole-measure rest width significantly http://code.google.com/p/lilypond/issues/detail?id=1880 I can'

Re: Issue 1848 in lilypond: Lilypond-book: Give images 1mm less linewidth

2011-09-11 Thread lilypond
Updates: Status: Verified Comment #4 on issue 1848 by philehol...@googlemail.com: Lilypond-book: Give images 1mm less linewidth http://code.google.com/p/lilypond/issues/detail?id=1848 Confirmed as geting rid of all those nasty black bars on images in Learning :-)

Re: Issue 1849 in lilypond: Fix memleak: temporary skyline objects for systems were never deleted

2011-09-11 Thread lilypond
Updates: Status: Verified Comment #4 on issue 1849 by philehol...@googlemail.com: Fix memleak: temporary skyline objects for systems were never deleted http://code.google.com/p/lilypond/issues/detail?id=1849 Verified as pushed on Sept 1. _

Re: Issue 1584 in lilypond: removing parser DIGIT rule

2011-09-11 Thread lilypond
Updates: Labels: fixed_2_15_11 Comment #6 on issue 1584 by philehol...@googlemail.com: removing parser DIGIT rule http://code.google.com/p/lilypond/issues/detail?id=1584 (No comment was entered for this change.) ___ bug-lilypond mailing li

Re: Issue 1584 in lilypond: removing parser DIGIT rule

2011-09-11 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review Comment #5 on issue 1584 by d...@gnu.org: removing parser DIGIT rule http://code.google.com/p/lilypond/issues/detail?id=1584 Actually, I have reread the patch as diff again. It is straightforward and simple. It passes regtests (yes

Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2

2011-09-11 Thread lilypond
Comment #15 on issue 1780 by reinhold...@gmail.com: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2 http://code.google.com/p/lilypond/issues/detail?id=1780 That's a regression. The regtest should print out "0.19" (i.e. two decimals after the comm

Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented

2011-09-11 Thread Reinhold Kainhofer
Am Saturday, 10. September 2011, 21:22:30 schrieb lilyp...@googlecode.com: > Comment #32 on issue 1776 by percival.music.ca: Doc: NR - Polymetric > Notation \compoundMeter isn't documented > http://code.google.com/p/lilypond/issues/detail?id=1776 > > 2.14.2, and then clear out everything in Docume

Re: Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly

2011-09-11 Thread lilypond
Comment #1 on issue 1880 by tdaniels...@googlemail.com: Presence of a bar number changes whole-measure rest width significantly http://code.google.com/p/lilypond/issues/detail?id=1880 Here's a simple work-around (by analogy with textLengthOn/Off): barNumberLengthOn = { \override Score.BarN

Re: Issue 1584 in lilypond: removing parser DIGIT rule

2011-09-11 Thread lilypond
Updates: Status: Started Owner: d...@gnu.org Labels: -Patch-needs_work Patch-review Comment #4 on issue 1584 by d...@gnu.org: removing parser DIGIT rule http://code.google.com/p/lilypond/issues/detail?id=1584 Rietveld http://codereview.appspot.com/4311041> now carries a w

Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings

2011-09-11 Thread lilypond
Updates: Labels: -Priority-Low -Patch-push -fixed_2_15_10 fixed_2_15_11 Comment #9 on issue 1805 by tdaniels...@googlemail.com: Ambitus engraver produces false warnings http://code.google.com/p/lilypond/issues/detail?id=1805 The fix didn't make it in 2.15.10. It's in 2.15.11 __

Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings

2011-09-11 Thread lilypond
Comment #8 on issue 1805 by philehol...@googlemail.com: Ambitus engraver produces false warnings http://code.google.com/p/lilypond/issues/detail?id=1805 Not verified. I still get the error message on 2.15.10. ___ bug-lilypond mailing list bug-lil

Re: Issue 905 in lilypond: LilyPond should accept UTF-8 BOM signatures even if preceded with other chars

2011-09-11 Thread lilypond
Updates: Status: Verified Comment #6 on issue 905 by philehol...@googlemail.com: LilyPond should accept UTF-8 BOM signatures even if preceded with other chars http://code.google.com/p/lilypond/issues/detail?id=905 (No comment was entered for this change.) ___

Re: Issue 724 in lilypond: Staves that begin with an accidental should have more space before their first note.

2011-09-11 Thread lilypond
Updates: Status: Verified Comment #8 on issue 724 by philehol...@googlemail.com: Staves that begin with an accidental should have more space before their first note. http://code.google.com/p/lilypond/issues/detail?id=724 (No comment was entered for this change.)

Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly

2011-09-11 Thread lilypond
Status: Accepted Owner: Labels: Type-Ugly New issue 1880 by philehol...@googlemail.com: Presence of a bar number changes whole-measure rest width significantly http://code.google.com/p/lilypond/issues/detail?id=1880 Reported by Reinhold: If there is bar number printed after a measure, a

Re: Presence of a bar number changes whole-measure rest widthsignificantly

2011-09-11 Thread Phil Holmes
"Reinhold Kainhofer" wrote in message news:201109082343.26053.reinh...@kainhofer.com... If there is bar number printed after a measure, a full measure rest will be much longer than if there is no bar number printed. Simple example attached. A bar number should not have an influence on horizon

Issue 1879 in lilypond: Packed-spacing works improperly with Mensural_ligature_engraver and Vaticana_ligature_engraver

2011-09-11 Thread lilypond
Status: Accepted Owner: Labels: Type-Ugly New issue 1879 by philehol...@googlemail.com: Packed-spacing works improperly with Mensural_ligature_engraver and Vaticana_ligature_engraver http://code.google.com/p/lilypond/issues/detail?id=1879 Marek Klein reports (NB I have not checked this a

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

2011-09-11 Thread lilypond
Updates: Status: Verified Comment #7 on issue 723 by philehol...@googlemail.com: wrong horizontal alignement of pedal brackets with a second inside a chord http://code.google.com/p/lilypond/issues/detail?id=723 (No comment was entered for this change.) __

Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-09-11 Thread lilypond
Comment #8 on issue 1529 by philehol...@googlemail.com: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 Looking at the output for the 2.15.10 regtests (there's quite a bit to scroll down...) I still see the -Writing/+Writing

Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax

2011-09-11 Thread lilypond
Comment #6 on issue 1110 by arnowas...@gmail.com: Wrong octave of repetition chord with \relative and #{ #} syntax http://code.google.com/p/lilypond/issues/detail?id=1110 2.13.4? Are you sure? I could not make release/2.13.4-1 make "compile" the above snippets...

Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented

2011-09-11 Thread lilypond
Comment #36 on issue 1776 by pkx1...@gmail.com: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 Neil, thanks for that. new patch uploaded with (hopefully) corrected snippet edit as well. http://codereview.appspot.com/4837

Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display

2011-09-11 Thread lilypond
Updates: Labels: -Patch-new Patch-needs_work Comment #13 on issue 1503 by pkx1...@gmail.com: Feature request: simplify jazz chord display http://code.google.com/p/lilypond/issues/detail?id=1503 Passes make but fails reg test comparison. --snip-- ocessing cf/lily-2272dc04 Processing

Re: Issue 1572 in lilypond: Change chord name separator and inversion separator, separately

2011-09-11 Thread lilypond
Updates: Labels: -Patch-new Patch-needs_work Comment #7 on issue 1572 by pkx1...@gmail.com: Change chord name separator and inversion separator, separately http://code.google.com/p/lilypond/issues/detail?id=1572 Passes make but fails reg test: --snip-- Processing cf/lily-2272dc04 Pr

Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2

2011-09-11 Thread lilypond
Updates: Labels: -Patch-new Patch-review Comment #14 on issue 1780 by pkx1...@gmail.com: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2 http://code.google.com/p/lilypond/issues/detail?id=1780 Passes make. There is one reg test that shows u