Re: compilable lilypond-book templeat

This was just posted on the list by Nick Payne . Hope it helps. On Fri, Jan 31, 2014 at 8:36 PM, MING TSANG wrote: > Hi, lilyponders: > Over the years (since lilypond v2.14) I have coded 25+ hymns for our > choir. I like to put them in book form. Is there a lilypond-book template > available (

Re: Guitars with capos

Hello Hilary: Please excuse a short notation question! This is a fun question! What's the preferred way of notating music for a guitar with capo? Sounding pitch, or as a transposing instrument (so that a guitar capoed on the third fret is effectively a guitar in E flat)? This would depend upon

Guitars with capos

Please excuse a short notation question! What's the preferred way of notating music for a guitar with capo? Sounding pitch, or as a transposing instrument (so that a guitar capoed on the third fret is effectively a guitar in E flat)? -- Hilary ___ lil

compilable lilypond-book templeat

Hi, lilyponders: Over the years (since lilypond v2.14) I have coded 25+ hymns for our choir. I like to put them in book form.  Is there a lilypond-book template available (compilable - just include my 25+ hymns)? I like to have title page, table of content and each hymn starts on a new page.  If

Re: Producing a title page

On 31/01/14 04:48, David Sumbler wrote: Having now got LilyPond 2.18.0 set up on my two machines, thanks to all the help from the list, I have now started trying to adjust the output of the pieces I have so far produced. I have used \header blocks for title, composer etc., and these are working

RE: Producing a title page

Peter Gentry wrote >> >>Message: 3 >>Date: Thu, 30 Jan 2014 17:48:42 + >>From: David Sumbler < > david@.co > > >>To: > lilypond-user@ >>Subject: Producing a title page >>Message-ID: <1391104122.2284.67.camel@vesta> >>Content-Type: text/plain; charset="UTF-8" >> >>Having now got LilyPond 2.

RE: [SPAM] lilypond-user Digest, Vol 134, Issue 196

>Date: Fri, 31 Jan 2014 03:32:27 -0800 (PST) >From: SoundsFromSound >To: lilypond-user@gnu.org >Subject: RE: Producing a title page >Message-ID: <1391167947603-158681.p...@n5.nabble.com> >Content-Type: text/plain; charset=us-ascii > >Peter Gentry wrote >>> > >Peter, >I tried to use your code and

Re: Producing a title page

David Sumbler writes: > On Thu, 2014-01-30 at 11:09 -0800, Mark Stephen Mrotek wrote: >> David, >> >> Putting a "\pagebreak" after the first header and before the first score >> seems to accomplish what you want. >> >> Mark > > Thanks for that - it seems to be one permutation I hadn't tried! >

Re: Producing a title page

I've just tried the code. An eps file is missing too : delete the corresponded line (line # 126) Cheers, Pierre ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Producing a title page

2014-01-31 MING TSANG : > > I tried to use your code and I kept getting an error: > > error: syntax error, unexpected end of input > \pageBreak > I suppose a "}" is missing at the end of the code. Cheers, Pierre ___ lilypond-user mailing list lilypond-u

RE: Producing a title page

  6. RE:Producing a title page (SoundsFromSound) -- Message: 6 Peter, I tried to use your code and I kept getting an error: error: syntax error, unexpected end of input \pageBreak Do you know how to remedy this? I a

RE: Producing a title page

On Thu, 2014-01-30 at 11:09 -0800, Mark Stephen Mrotek wrote: > David, > > Putting a "\pagebreak" after the first header and before the first score > seems to accomplish what you want. > > Mark Thanks for that - it seems to be one permutation I hadn't tried! I must confess that I find some aspe

RE: Producing a title page

Peter Gentry wrote >> >>Message: 3 >>Date: Thu, 30 Jan 2014 17:48:42 + >>From: David Sumbler < > david@.co > > >>To: > lilypond-user@ >>Subject: Producing a title page >>Message-ID: <1391104122.2284.67.camel@vesta> >>Content-Type: text/plain; charset="UTF-8" >> >>Having now got LilyPond 2.

RE: Producing a title page

> >Message: 3 >Date: Thu, 30 Jan 2014 17:48:42 + >From: David Sumbler >To: lilypond-user@gnu.org >Subject: Producing a title page >Message-ID: <1391104122.2284.67.camel@vesta> >Content-Type: text/plain; charset="UTF-8" > >Having now got LilyPond 2.18.0 set up on my two machines, >thanks to al

Re: vertical spacing inside a \right-column

On 01/31/2014 10:29 AM, Martin Tarenskeen wrote: Hi, I am creating a header with something like composer = \markup { \tiny \right-column { [...] What should I do if I want the lines inside the composer column to be vertically spaced closer to each other, so that the column takes less ver

Re: vertical spacing inside a \right-column

Martin Tarenskeen writes: > Hi, > > I am creating a header with something like > > composer = \markup { > \tiny > \right-column { > "Words and Music by:" > " X," > " Y," > "and Z" > } > } > > What should I do if I want the lines inside the composer c

Re: Non-customary clef printing

Marc Hohl writes: > Hi David, > > Am 30.01.2014 07:18, schrieb David O'Donnell: >> I am trying to replicate an older score, where the the clef changes at >> the beginning of the line. However, unlike Lilypond's default, the old >> clef and the key signature are printed and then immediately follow

vertical spacing inside a \right-column

Hi, I am creating a header with something like composer = \markup { \tiny \right-column { "Words and Music by:" " X," " Y," "and Z" } } What should I do if I want the lines inside the composer column to be vertically spaced closer to each other,

Re: Non-customary clef printing

Hi David, Am 30.01.2014 07:18, schrieb David O'Donnell: I am trying to replicate an older score, where the the clef changes at the beginning of the line. However, unlike Lilypond's default, the old clef and the key signature are printed and then immediately following that, the new clef is printe