1 .TH "LilyPond" "1" "1998" "The LilyPond package" "The GNU Project Music Typesetter"
5 LilyPond \- the GNU Music Typesetter
10 \fBlilypond\fP [OPTION]\&.\&.\&. [MUDELA-FILE]\&.\&.\&.
17 LilyPond is the GNU Project music typesetter\&. This program can print
18 beautiful sheet music from a music definition file\&. It can also play
19 mechanical performances to a MIDI file\&. Features include multiple
20 staffs, meters, clefs, keys, lyrics, versatile input language, cadenzas,
21 beams, slurs, triplets, formatting scores, part extraction\&. It includes
22 a nice font of musical symbols\&.
29 .IP "-I,--include=FILE"
30 add \fBFILE\fP to the search path for input files\&.
32 This disables TeX output\&. If you have a \emidi definition, it will do the
34 .IP "-d,--dependencies"
35 Also output rules to be included in Makefile\&.
37 Turn debugging info on\&. GNU LilyPond reads the file \fB\&.dstreamrc\fP,
38 which lists what functions and classes may produce copious debugging
41 Switch on any experimental features\&. Not for general public use\&.
43 Show the warranty with which GNU LilyPond comes\&. (It comes with
45 .IP "-o,--output=FILE"
46 Set the default output file to \fBFILE\fP\&.
48 Show a summary of usage\&.
50 Set init file to \fBFILE\fP (default: \fBinit\&.ly\fP)\&.
51 .IP "--include, -I=DIRECTORY"
52 Add \fBDIRECTORY\fP to the search path for input files\&.
53 .IP "--ignore-version, -V"
54 Make incompatible mudela version non-fatal\&.
55 .IP "--find-fourths, -Q"
56 Warn about melodic intervals larger than a fourth\&. Useful for
57 converting absolute octave mode stuff to relative octaves\&.
61 This is an overview of the features that GNU LilyPond supports\&. For
62 details on how to use them, you should consult the Mudela tutorial,
63 which is included with the package\&.
66 ASCII script input, with identifiers (for music reuse),
67 customizable notenames, customisable fontset\&.
69 MIDI output lets you check if you have entered the correct notes\&.
71 MIDI to Mudela conversion through the mi2mu program\&.
73 Multiple staffs in one score\&. Each staff can have different meters\&.
75 Beams, slurs, ties, chords, super/subscripts (accents and text)
76 triplets, general n-plet (triplet, quadruplets, etc\&.), lyrics,
77 transposition dynamics (both absolute and hairpin style)\&.
79 Multiple voices within one staff; beams optionally shared
80 between voices\&. Up to four voices is handled cleanly\&.
82 Multiple scores within one input file\&. Each score is output to
85 Clef changes, meter changes, cadenza-mode, key changes, repeat bars\&.
89 GNU LilyPond is copyright 1996-1998 by its authors\&. GNU LilyPond is
90 distributed under the terms of the GNU General Public License\&. GNU LilyPond
91 is provided without any warranty what so ever\&.
92 GNU LilyPond may be freely distributed\&. For further information consult
93 the GNU General Public License, from the file \fBCOPYING\fP\&.
97 There is an extensive list of todoes and bugs\&. See \fBTODO\fP\&. If you
98 have a problem you should try to find out
101 If the bug has been fixed in a newer release\&.
103 If the bug has been found earlier, consult \fBTODO\fP and \fBBUGS\fP\&.
105 If you have found a bug, then you should send a bugreport\&.
108 Send a copy of the input which causes the error\&.
110 Send a description of the platform you use\&.
112 Send a description of the LilyPond version you use
113 (with compile/configure options please)\&.
115 Send a description of the bug itself\&.
117 Send it to bug-gnu-music@gnu\&.org <bug-gnu-music@gnu\&.org> (you don\'t have to subscribe
118 to this mailinglist)\&.
121 .IP "\fBinit\&.ly\fP"
122 The initialisation file with symbol tables etc\&. It
123 includes files from the directory \fBinit/\fP\&.
125 manspagesection(environment)
128 additional directories for finding lilypond data\&. The
129 format is like the format of \fBPATH\fP\&.
131 selects the language for the warning messages of LilyPond\&.
135 Lots of them\&. See \fBTODO\fP and \fBBUGS\fP
140 On technical details of LilyPond
142 On the input format\&. This is a LilyPond-enhanced LaTeX document\&.
144 Goals of the GNU LilyPond project\&.
146 The GNU LilyPond FAQ list
148 has her own webpage\&. This webpage contains the MIDI, GIF and PS files for
149 some standard music files\&. It also has the complete LilyPond documentation
152 updated very frequently, the latest version is always available at:
153 ftp://pcnov095\&.win\&.tue\&.nl/pub/lilypond\&. This FTP site is mirrored
154 at a number of sites; consult the project web pages for information
157 For programs which are part of the GNU music project, the following
158 mailing list have been setup:
160 .IP "info-gnu-music@gnu\&.org <info-gnu-music@gnu\&.org>"
161 For information on the GNU Music project, to subscribe: send mail with
162 subject "subscribe" to info-gnu-music-request@gnu\&.org <info-gnu-music-request@gnu\&.org>
163 .IP "help-gnu-music@gnu\&.org <help-gnu-music@gnu\&.org>"
164 For help with programs from the GNU music project\&. To subscribe: send
165 mail with subject "subscribe" to help-gnu-music-request@gnu\&.org <help-gnu-music-request@gnu\&.org>
166 .IP "bug-gnu-music@gnu\&.org <bug-gnu-music@gnu\&.org>"
167 If you have bugreports, you should send them to this list\&. If you want
168 to read all bugreports, you should subscribe to this list\&. To
169 subscribe: send mail with subject "subscribe" to
170 bug-gnu-music-request@gnu\&.org <bug-gnu-music-request@gnu\&.org>
171 .IP "gnu-music-discuss@gnu\&.org <gnu-music-discuss@gnu\&.org>"
172 For discussions concerning the GNU Music project, to subscribe: send
173 mail with subject "subscribe" to
174 gnu-music-discuss-request@gnu\&.org <gnu-music-discuss-request@gnu\&.org>
176 Announces of new versions will be sent to info-gnu-music and
181 GNU LilyPond has no connection with the music package Rosegarden, other
182 than the names being similar (:-)
186 (for a detailed changelog, see \fBNEWS\fP)
188 GNU LilyPond\'s roots lie in MPP, a preprocessor to the rather arcane
189 MusiXTeX macro package for TeX\&. A friend of mine, Jan Nieuwenhuizen
190 wrote the first 44 versions (0\&.01 to 0\&.44), then his program caught my
191 attention, and I was slowly sucked in to the interesting problem of
192 easily producing beautifully printed music\&. I contributed some
193 code\&. We soon realised that MPP\'s design was too fundamentally broken
194 to be repaired, so it was decided to rewrite MPP\&. We debated a lot about
195 the requirements to an inputformat (fall 1995)\&. I sat down and started
196 with a parser-first, bottom-up rewrite called mpp95 (which totally
197 failed, obviously)\&.
199 After long and hard thinking, I came up with an algorithm for the
200 horizontal spacing of multiple staffs (april 1996) I coded it (and did
201 not test it)\&. After starting with this fundamental piece, I slowly
202 added the stages which come before spacing, and after\&. A half year
203 later, I had a first working version, (october 1996)\&. I announced
204 Patchlevel 0\&.0\&.7 (or 8) to the mutex list after asking some technical
205 details on spacing; it was downloaded approximately 4 times\&. Then I
206 got the hang of it, and in the subsequent two months, I coded until it
207 had doubled in size (pl 23)\&.
209 Most the other history is described in the NEWS file\&. The first large
210 scale release (0\&.1) was done after approximately 78 patchlevels on
215 Please consult the documentation file \fBAUTHORS\&.txt\fP for more detailed
216 information, and small contributions\&.
219 Han-wen Nienhuys <hanwen@cs\&.uu\&.nl>
220 http://www\&.cs\&.uu\&.nl/people/hanwen
222 Jan Nieuwenhuizen <janneke@gnu\&.org>
223 http://www\&.xs4all\&.nl/~jantien