Re: ghostscript dependancy in the autopackage

Guy Banay writes: > The Lilypond autopackage (version 2.6.1) will not install on systems > without Ghostscript >= 8.15 despite GS being an optional runtime > dependancy and lilypond can run without it. What does `will not install' mean? Did you try the full package? > It would be more appropria

Re: lily/parser.yy rev 1.476

On 27-Jul-05, at 4:10 AM, Sven Axelsson wrote: * lily/parser.yy (score_body): \score can only begin with Music. No, it can begin with \header too, and this change (i think) is causing errors when I try version 2.7.3. I believe that this is a new feature. Han-Wen, could you confirm? \score _

Re: Documentation bug: Section 7.3.2

On 18-Jul-05, at 4:00 AM, Mats Bengtsson wrote: I would be very surprised if these left hand and right hand double quotes didn't exist in Unicode. On the other hand, then the example will be just one of many examples showing how to use Unicode characters, so maybe it can be removed anyway.

Re: aikenHeads shapenote "fa" half note is updise down.

Bob Broadus wrote: Thanks for lilypond, and especially for the recent addition of shape notes. I noticed that when "fa" is a half note using the aikenHeads, it is upside-down. It seems that in "feta-bolletjes.mf" in the 2.7.2/share/source folder at around line 1207: fet_beginchar ("half fa up

Re: Beam over repeat bar

On 26-Jul-05, at 5:47 PM, Fairchild wrote: Documentation says "no auto beams will be put over repeat bars." This code: \version "2.4.6" \score { { \time 2/4 \repeat volta 2 { \partial 8*1 e'8 f'8 g' a' } \partial 8*1 b'8 c''4 d''8 \bar "|." } } Looks ok on 2.7.3; no beams over the repeat.

lily/parser.yy rev 1.476

* lily/parser.yy (score_body): \score can only begin with Music. No, it can begin with \header too, and this change (i think) is causing errors when I try version 2.7.3. -- Sven Axelsson ___ bug-lilypond mailing list bug-lilypond@gnu.org http://list

ghostscript dependancy in the autopackage

The Lilypond autopackage (version 2.6.1) will not install on systems without Ghostscript >= 8.15 despite GS being an optional runtime dependancy and lilypond can run without it. It would be more appropriate imho to issue a warning but let the installation complete, especially considering that even

Bad spacing with short notes before the bar line

Hi, Although LilyPond is generally very good at spacing, I've found that 1/32 notes at the end of a measure are often displayed much too close from the bar, especially if they are down-stemed. I've had a look at some traditionally engraved scores : everywhere there is a minimal distance between t

aikenHeads shapenote "fa" half note is updise down.

Thanks for lilypond, and especially for the recent addition of shape notes. I noticed that when "fa" is a half note using the aikenHeads, it is upside-down. It seems that in "feta-bolletjes.mf" in the 2.7.2/share/source folder at around line 1207: fet_beginchar ("half fa up head", "d1fa"); shoul

Barline bug with Staff Timing_engraver?

Looking at the final barline in this 2.7.0 snippet ... begin snippet = \score { \new StaffGroup << \new Staff { \clef treble \time 3/4 d'4 d'4 d'4 | d'4 d'4 d'4 | d'4 d'4 d'4 | d'4 d'4 d'4 \bar "|." | } \new Staff {

Re: text markup extra space in {}

Graham Percival wrote: This is a better example of that \header markup bug I reported yesterday. % fink 2.7.3, extra space between second Foo and . {c'4^\markup{Foo. {Foo}.} } not a bug. Markup is whitespace insensitive, so {Foo}. is like { Foo } . -- Han-Wen Nienhuys - [EMAIL PROT

text markup extra space in {}

This is a better example of that \header markup bug I reported yesterday. % fink 2.7.3, extra space between second Foo and . {c'4^\markup{Foo. {Foo}.} } ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-