Re: Advice concerning multiple editions

[Urs Liska]

Am 7. Januar 2018 16:23:23 MEZ schrieb Kieren MacMillan <address@hidden>:
>Hi Ralph,
>
>Here are my suggestions.
>
>> Some background:
>> I have a collection of over 500 tunes (mostly 32 bars) that I've
>transposed and would like to share as PDFs via the internet. I'm
>planning on 4 formats:
>> 1) small font, for myself, all the tunes as a collection;
>> 2) large font, for the public, most of the tunes, as individual
>tunes;
>> 3) large font, for the public, most of the tunes as a collection; and
>> 4) small font, for the public, most of the tunes as a collection.
>
>So far, so good.

It is possible to create an entry file that includes selected music and 
selected styles. This can be configured through command line options or 
otherwise, depending on the use case and the layout of the existing files. 

>
>> The line and page breaking for the collections will vary among the
>three collections.
>
>Here, the edition-engraver (EE) works quite well: you can create a
>shared break set (e.g. "4 systems of 4 bars each") or a break set for
>individual songs, as you need.


The page-layout package is a wrapper that makes this even easier. 

But the "plain" EE is the tool of choice for handling layout corrections that 
become necessary for a given format. 

>
>> The titleing will also vary between large font and small font
>versions of the tunes.
>
>You just need to create one scoreTitleMarkup and bookTitleMarkup for
>each of the four formats.
>
>> Some of the tunes have multiple names, so I would like to have an
>index, preferably at the beginning of the document. Also some
>introductory text (probably no more than a couple of pages) and, if
>possible, Tables of Contents by tune type (jig, reel, waltz, etc.).
>
>Personally, I would generate all of the PDFs in Lilypond, and then use
>LaTeX to add text and bind it all up.
>That doesn't, of course, solve the problem of an automated index — I
>have no experience with that, and thus am of no help there.

What you will need is the appropriate Latex commands for TOC and index  entries 
at the proper places in the Latex file. 

What I would do here is probably write an external script (e.g. in Python) that 
triggers Lily Pond and generates the Latex file along the way. 

On thing to consider is pagination. I would probably do it in Latex completely. 

Best
Urs

>
>> The music is the same in all versions; i.e., notes, clefs, slurs,
>ties, dynamics, repeats, etc.
>
>That does make it easier (although the EE is great for managing
>differences between editions, e.g. performance clef versus full score
>clef).
>
>> My problem at the moment is that I do not know if I can index within
>LilyPond (with multiple names per tune)
>
>I believe you can… but, again, I have no personal experience to share.
>
>> what the most efficient way is of dealing with the line and page
>breaking and titleing issues.
>
>Either the EE (as suggested above), or David K's \bar-keeper function.
>
>Best of luck! Looking forward to hearing what you end up doing, and how
>well it went.
>
>Best regards,
>Kieren.
>________________________________
>
>Kieren MacMillan, composer
>‣ website: www.kierenmacmillan.info
>‣ email: address@hidden
>
>
>_______________________________________________
>lilypond-user mailing list
>address@hidden
>https://lists.gnu.org/mailman/listinfo/lilypond-user