I'm reviving this thread from last year. What I want is a way to \include files as if at toplevel inside a \book form. I want each to be processed as if it were in a separate invocation of LilyPond. I would like to be able to compile these as separate files or as parts of a book, but produce the exact same output (except for page numbers) with PDF bookmarks and a table of contents generated at the beginning of the output file. I can assemble PDFs using LaTeX, but the file will be much, much smaller if LilyPond does the assembly, because each separate PDF has its own copy of the fonts for that file.
On Mon, Feb 12, 2024 at 2:10 PM Eric Benson <[email protected]> wrote: > I have a growing collection of one- or two-page scores that I want to > assemble into books, each with a table of contents. I've been using LaTeX's > pdfpages package for this purpose, just pulling together all the LilyPond > pdf output with page numbers added and a ToC on the front. This method > works pretty well and is in fact completely independent of LilyPond itself, > but I was thinking that the resulting assembled PDF files would be much > smaller if they shared font info and wondered if anyone has advice on > making a LilyPond book using \markuplist \table-of-contents with \tocItem > and \include for each separate score, while also maintaining the ability to > build each score as a separate PDF file. >
