[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Patch for lilypond-book to support separate titling and indexing in
From: |
Han-Wen Nienhuys |
Subject: |
Re: Patch for lilypond-book to support separate titling and indexing in LaTeX |
Date: |
Thu, 27 Apr 2006 15:58:08 +0200 |
User-agent: |
Thunderbird 1.5 (X11/20060313) |
Hello Michael,
thanks for your patch!
Michael Haynie schreef:
I've been working on a largish collection of hymns for the last several
years. The collection includes lead sheets, piano scoring, and
orchestral arrangements, and a hymnal. There are now several thousand
files in the source base. As you might imagine, automation is really
important to my sanity <G>. To support that, I've modified
lilypond-book to help me with the construction of the hymnal. This
patch allows me to set up titling and indexing in LaTeX (which it does
very well), while allowing Lilypond to engrave the music. So: the patch
makes it possible to automatically construct a fairly elaborate hymnal
type work, but at the cost of making installation a little more difficult.
Would it be better to generate the macros in the source directory and
automatically generate the input statement? (I think this might be hard
to do, but I see that we do something similar with \usepackage{graphics}).
I think the file should be generated/copied to the output directory.
Since files in that directory are surely seen by latex, it's a safe choice.
The lilypond invocation is modified to include '-H all' by default.
Agreed?
No problem.
I'd be happy to contribute a writeup on using this scheme to either the
documentation, or the snippet repository. What would you prefer? I can
give detailed instructions on the whole process from arranging the pages
to to constructing the indexing automatically, to constructing the
signatures for binding.
Please do; I'm still a bit in doubt whether the header file should be
part of LilyPond proper or an add-on. In any event, it should use lily
style naming, eg.
lilypond-latex-system-macros.tex
also, detailed information on making a book with using should probably
be in a separate document, since that process is in a large part
external to lily.
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com