Interesting. Very clean from a compatibility point-of-view.
I guess lilypondfile would call a macro if was defined, and include
everything otherwise? Maybe \includeLilypondSystems{}
Many users might have no idea how to define the macro to include a
sequence of generated files.
We should provide a macro for the default case (include everything, in
order) and a common alternate (include n systems, starting with the
kth one). Even though I've written 2000 page documents in LaTeX, I'd
have to think about how to do that for a bit.
I like the -H option as well -- it will greatly simplify invocation
for this case, and cases like it.
On Nov 30, 2005, at 7:08 AM, Bernard Hurley wrote:
I have thought of a better way of doing this:
modify \lilypondfile so that it takes an optional argument as in:
lilypondfile[reference]{mysong.ly}
The idea is that without the optional parameter it would work as before,
but with the parameter, it would work as follows:
1] the eps files, (e.g. lily-1915112629-1.eps, lily-1915112629-2.eps)
would be generated as before, but _not_ included in the tex file.
2] there would be tex commands automatically generated so that:
\referenceBase would have value base name of generated files
(lily-1915112629 in this case)
\referenceCount would have value number of eps files generated.
maybe we could also have:
\referenceFile defined as the file name (mysong.ly in this case)
This would mean that it would be easy to generate names of the .eps
files, any files containing headers (e.g. lily-1915112629.title) etc,
these could then be input or dealt with in other ways. It opens up all
sorts of possiblities. For instance if you wanted to put the lilypond
source code into you document you could construct the name of it (in
this case lily-1915112629.ly). You would have complete control over how
and where the files are processed. (So if you had a contents page that
used a scaled down, and clipped version of the first system of a son,
this could be done).
I think I know how to do this, but there are a few minor bugs in
lilypondbook that need fixing first. I expect to be able to submit a
patch to the developer list in the next two weeks.
It might also be a good idea if lilypond-book could take a -H option
that would then be passed on to lilypond.
--
Bernard Hurley <address@hidden>
_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user