On 27/04/14 16:13, Urs Liska wrote:
Am 27.04.2014 00:22, schrieb Knute Snortum:
Okay, that looks good. But there are two things: First, can the
files be
*.ly files instead of *.ily files?
As Paul said, the file extension is purely a convenience for human
readers. When \include-ing a file LilyPond will simply read in that
file and treat it exactly as if its content would have been written
directly in the original input file.
And if not, will *.ily files compile
standalone? (People will still want to download just one movement.)
The idea is to use the *.ily files as pure includable files (hence
.IncludableLY) and _not_ to compile them standalone.
In your case you would have to find some cascading set-up, writing the
content of the music in one file, the score structure of this
individual piece in another one and yet a third one for the whole
piece that pulls in the individual movements.
When I'm setting up movements for a piece where I want to be able to
both build them stand-alone and \include them in another file to build
the entire piece, I put the \paper, \header, and \score blocks at the
end of the movement file, surrounded by a comment block:
%{
\paper {
% \paper stuff here
}
\header {
% \header stuff here
}
\score {
% \score stuff here
}
%}
If I want to build the movement on its own, I change the %{ to %%{,
which comments out the comment block beginning, so that \paper, \header,
and \score are all parsed. If I'm including the movement in another file
as part of a complete piece, I just need to change %%{ to %{ so that
\paper, \header, and \score blocks are all commented out.
Nick
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
