RE: Overriding a global declaration

I am so…. grateful for your help here and enclose my version with adjustments if you are interested.

I found that adding a \pagebreak inside a bookpart in order to place tunes 3 & 4 on separate pages led to unwanted changes in pagination. When I placed tune 4 in its own bookpart everything was fine. In my old structure it was possible to separate tunes with pagebreaks.

I also added a new section with two short tunes on one page. This was also successful.

I now understand book and bookpart structure better. I don’t think Finale or Sibelius can offer the same flexibility as that available in Lilypond – the problem is the learning curve!

John McWilliam

Sent from Mail for Windows 10

From: Thomas Morley
Sent: Wednesday, August 7, 2019 9:54 PM
To: John McWilliam
Cc: address@hidden
Subject: Re: Overriding a global declaration

Am Mi., 7. Aug. 2019 um 20:37 Uhr schrieb John McWilliam

<address@hidden>:

> Following my previous mail I have tried to simplify my problem in a book containing three tunes:

> A normal tune with 13 lines of Music where the last line should spill over into the next page. It doesn’t when compiled together with…

> A so called reduced tune also with 13 lines which now fits onto one page after following suggestions from Thomas Morley.

> The final tune is normal and should perform as number 1 and spill over onto the next page – it doesn’t.

> Simply stated, I want to be able to reduce the size of one tune in a book where the majority of tunes have a larger global definition of staff size. The files are a simple and small as I could possibly make them at the same time illustrating my dilemma.

> John McWilliam

> From: John McWilliam

> Sent: Wednesday, August 7, 2019 8:12 PM

> Reply to Thomas Morley:

> Still not out of the woods yet. I think it is due to the fact that your example creates a bookpart in the Tune file and then again in the Book file. If I remove the book deklaration from the Book file I loose my Table of Contents! Also, isn’t the \paper section unnecessary if it appears in BP_format.ily??

> Sorry if my questions appears basic in nature – my level of experience using Lilypond is limited.

Hi John,

please check before posting your example(s) work. You used relative

paths for the includes, which don't work with your stripped down files

...

I'd still recommend to use /bookpart, even more: wherever you insert

\pageBreak you should think about to start/end a bookpart.

(To keep the title page I didn't wrap your table-of-content into an

extra bookpart. Nevertheless for own projects I tend to create a

title-page indepent from book-header, then the toc in an own bookpart,

then the other bookparts)

Admittedly including a bookpart into another bookpart will not work,

so you shouldn't state a /bookpart in the to-be-included file, but

wrap it around the tocItem/Section and the \include when called in

\book

You may need to pay more attention for correct headers, this is the

only disadvantage I know.

If you do so (with the correct syntax) you can have different settings

for every bookpart via \paper.

NB a general \paper will affect every score/bookpart of the book.

Btw, in your BP_format.ily you write

ragged-bottom = ##t

Why? It causes some warnings, I've commented it without disadvantage

as far as I can tell.

So the only difference in \paper of the "reduced" bookpart is:

ragged-last-bottom = ##f

Maybe one could go for `page-count´ or `systems-per-page´ instead.

My code suggestions attached.

HTH,

Harm

From:	John McWilliam
Subject:	RE: Overriding a global declaration
Date:	Thu, 8 Aug 2019 11:39:01 +0200