lilypond-usage: Suggestions for writing files
5 Suggestions for writing files
*******************************
Now you’re ready to begin writing larger LilyPond input files – not just
the little examples in the tutorial, but whole pieces. But how should
you go about doing it?
As long as LilyPond can understand your input files and produce the
output that you want, it doesn’t matter what your input files look like.
However, there are a few other things to consider when writing LilyPond
input files.
• What if you make a mistake? The structure of a LilyPond file can
make certain errors easier (or harder) to find.
• What if you want to share your input files with somebody else? In
fact, what if you want to alter your own input files in a few
years? Some LilyPond input files are understandable at first
glance; others may leave you scratching your head for an hour.
• What if you want to upgrade your LilyPond file for use with a later
version of LilyPond? The input syntax changes occasionally as
LilyPond improves. Most changes can be done automatically with
‘convert-ly’, but some changes might require manual assistance.
LilyPond input files can be structured in order to be easier (or
harder) to update.
Menu
Info Catalog
lilypond-usage: External programs
lilypond-usage: Top
lilypond-usage: GNU Free Documentation License