Greetings;
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
impor
in hymnals.
Code making heavy use of this feature will appear in a separate patch,
since it deserves some discussion.
2006-04-09 Michael Haynie <[EMAIL PROTECTED]>
* scm/backend-library.scm (output-scopes): Support extracting all
defined header fields via '-H all&
t
evaluates to the name of an .eps file to include
[1] Actually this file does not need to be generated, but it only gets
written if it has changed and I find it easier to have all macros being
generated in the same place.
[2] Actually there is one exception - you cannot use "titling" as a
2005, at 8:08 AM, Bernard Hurley wrote:
Hi Michael,
On Tue, 2005-12-27 at 16:45 -0500, Michael Haynie wrote:
I had a good look at the proposed alternative mechanism as described
in
lilypondmacros. It mostly worked, but left me with a fair amount of
hand editing that would have to be revisit
I had a good look at the proposed alternative mechanism as described in
lilypondmacros. It mostly worked, but left me with a fair amount of
hand editing that would have to be revisited each time I rearranged the
songs in the book -- a *frequent* occurrence when I'm laying out a book
for fina
should be possible to gnerate libraries of songs
for
use in LaTeX.
e] You don't need all the generated files to use the macros. The ones
you need in addition to the .mac file are:
lilyXX-n.eps
lilyXX-verb.tex
lilyXX-verb1.tex
And if you are using the --psfo
OK, I'm back from Alaska. Sorry for the delay.
LaTeX macros with multiple parameters typically separate them with {},
so it would look like this:
\lilypondfile[options]{filename}{reference}
I thought we'd have lilypond-book provide the reference number, so I'm
not sure what the reference wo
