1 COMMENT(i don't get this)
2 mailto(janneke@gnu.org)
4 (PIPETHROUGH(echo -n `date '+%d/%b/%y'|tr '[a-z]' '[A-Z]'`)())
10 (The LilyPond package)
11 (The GNU Project Music Typesetter)
13 metalC(Automatically generated by yodl(1) from lilypond.yo.)
15 manpagename(LilyPond)(the GNU Music Typesetter)
19 bf(lilypond) [OPTION]... [MUDELA-FILE]...
23 includefile(../BLURB.in)
28 add file(FILE) to the search path for input files.
30 Disable TeX output. If you have a \midi definition, it will do the
32 dit(-d,--dependencies)
33 Also output rules to be included in Makefile.
35 Turn debugging info on. GNU LilyPond reads the file file(.dstreamrc),
36 which lists what functions and classes may produce copious debugging
39 Disallow untrusted code(\include) directives, backslashes in TeX()
40 code and named output.
42 Switch on any experimental features. Not for general public use.
44 Show the warranty with which GNU LilyPond comes. (It comes with
47 Set the default output file to file(FILE).
49 Show a summary of usage.
51 Set init file to file(FILE) (default: file(init.ly)).
52 dit(--include, -I=DIRECTORY)
53 Add file(DIRECTORY) to the search path for input files.
54 dit(--ignore-version, -V)
55 Make the incompatible mudela version warning non-fatal.
58 manpagesection(FEATURES)
60 This is an overview of the features that GNU LilyPond supports. For
61 details on how to use them, you should consult the Mudela tutorial,
62 which is included with the package.
66 it()ASCII script input, with identifiers (for music reuse),
67 customizable notenames, customisable fontset.
68 it()MIDI output lets you check if you have entered the correct notes.
69 it()MIDI to Mudela conversion through the mi2mu program.
70 it()Multiple staffs in one score. Each staff can have different time signatures.
71 it()Beams, slurs, ties, chords, super/subscripts (accents and text)
72 triplets, general n-plet (triplet, quadruplets, etc.), lyrics,
73 transposition, dynamics (both absolute and hairpin style).
74 it()Multiple voices within one staff; beams optionally shared
75 between voices. Up to four voices is handled cleanly.
76 it()Multiple scores within one input file. Each score is output to
78 it()Clef changes, meter changes, cadenza-mode, key changes, repeat bars.
81 manpagesection(DISCLAIMER)
83 GNU LilyPond is copyright 1996-1999 by its authors. GNU LilyPond is
84 distributed under the terms of the GNU General Public License. GNU LilyPond
85 is provided without any warranty what so ever.
86 GNU LilyPond may be freely distributed. For further information consult
87 the GNU General Public License, from the file file(COPYING).
89 manpagesection(PROBLEMS)
91 There is an extensive list of todoes and bugs. See the file
92 file(TODO) distributed with the sources. If you have a problem you
93 should try to find out
96 it()If the bug has been fixed in a newer release.
97 it()If the bug has been found earlier, consult file(TODO) and file(BUGS).
100 If you have found a bug, then we would appreciate it if you sent a
104 it()Send a copy of the input which causes the error.
105 it()Send a description of the platform you use.
106 it()Send a description of the LilyPond version you use
107 (with compile/configure options please).
108 it()Send a description of the bug itself.
109 it()Send it to email(bug-gnu-music@gnu.org); you don't have to be subscribed
116 The initialisation file with symbol tables etc. It
117 includes files from the directory
118 file(PREFIX/share/lilypond/ly/). (file(PREFIX) typically is file(/usr/local)
121 manspagesection(environment)
125 additional directories for finding lilypond data. The
126 format is like the format of file(PATH).
130 selects the language for the warning messages of LilyPond.
135 Lots of them. See file(TODO) and file(BUGS)
139 LilyPond comes with various other documentation files, but most are in
140 the form of manual pages. They are included in the source
141 package. Interesting documents include
145 Goals of the GNU LilyPond project.
147 The GNU LilyPond FAQ list
150 A further source for information is the website, which can be found at
151 lurl(http://www.lilypond.org/). The website contains on-line versions
155 GNU LilyPond is updated very frequently, the latest version is always
156 available at: lurl(ftp://ftp.cs.uu.nl/pub/GNU/LilyPond). This FTP
157 site is mirrored at a number of sites; consult the project web pages
158 for information about mirrors.
160 For programs which are part of the GNU music project, the following
161 mailing list have been setup:
164 dit(email(info-gnu-music@gnu.org))
165 For information on the GNU Music project, to subscribe: send mail with
166 subject "subscribe" to email(info-gnu-music-request@gnu.org)
167 dit(email(help-gnu-music@gnu.org))
168 For help with programs from the GNU music project. To subscribe: send
169 mail with subject "subscribe" to email(help-gnu-music-request@gnu.org)
170 dit(email(bug-gnu-music@gnu.org))
171 If you have bugreports, you should send them to this list. If you want
172 to read all bugreports, you should subscribe to this list. To
173 subscribe: send mail with subject "subscribe" to
174 email(bug-gnu-music-request@gnu.org)
175 dit(email(gnu-music-discuss@gnu.org))
176 For discussions concerning the GNU Music project, to subscribe: send
177 mail with subject "subscribe" to
178 email(gnu-music-discuss-request@gnu.org)
181 Announces of new versions will be sent to info-gnu-music and
184 manpagesection(REMARKS)
186 GNU LilyPond has no connection with the music package Rosegarden, other
187 than the names being similar :-)
193 it()nemail(Han-wen Nienhuys)(hanwen@cs.uu.nl)
194 lurl(http://www.cs.uu.nl/people/hanwen)
195 it()nemail(Jan Nieuwenhuizen)(janneke@gnu.org)
196 lurl(http://www.xs4all.nl/~jantien)
199 Please consult the documentation file file(AUTHORS) for more detailed
200 information, and small contributions.