1 \input texinfo @c -*- coding: latin-1; mode: texinfo; -*-
2 @setfilename lilypond.info
8 @dircategory GNU music project
13 Current version of the manual: 2.5.18
14 Please update this whenever you run convert-ly on the docs.
18 Distributions will want to install lilypond.info in postinstall, doing:
20 install-info --info-dir=/usr/share/info out/lilypond.info
24 * Prepend GNU for dir, must be unique.
26 * Do not list the `lilypond' node at toplevel, so that `info lilypond'
29 * List all commands in direntry.
31 @c * lilypond: (lilypond/lilypond)Running LilyPond. Invoking the
36 * LilyPond: (lilypond/lilypond). The GNU music typesetter.
37 * abc2ly: (lilypond/lilypond)Invoking abc2ly. Importing ABC.
38 * convert-ly: (lilypond/lilypond)Invoking convert-ly. Older LilyPond versions.
39 * etf2ly: (lilypond/lilypond)Invoking etf2ly. Importing Finale.
40 * lilypond-book: (lilypond/lilypond)LilyPond-book. Itegrating text and music.
41 * midi2ly: (lilypond/lilypond)Invoking midi2ly. Importing MIDI.
42 * mup2ly: (lilypond/lilypond)Invoking mup2ly. Importing Mup.
43 * musedata2ly: (lilypond/lilypond)Invoking musedata2ly. Importing MuseData.
48 @omfcreator Han-Wen Nienhuys and Jan Nieuwenhuizen
49 @omfdescription User manual of the LilyPond music engraving system
51 @omfcategory Applications|Publishing
55 @c don't remove this comment.
61 * Do not forget to create @cindex entries for new sections of text.
63 * Try not to use punctuation between an introductory sentence and
64 display material (music, example code).
66 * Do not refer to LilyPond in the text. The reader knows what the
67 manual is about. If you do, capitalization is LilyPond.
69 * If you explicitly refer to `lilypond', the program (or any other
70 command to be executed), say `@command{lilypond}'.
72 * Do not explicitly refer to the reader/user. There is no one else
73 besides the reader and the writer.
75 * Do not use abbreviations (don't, won't, etc.). If you do, use a
78 blabla blabla, i.e., blabla blabla
80 * Avoid fluff (``Notice that,'' ``as you can see,'' ``Currently,'').
82 * The use of the word `illegal' is inappropriate in most cases. Say
85 * Avoid long stretches of input code. Noone is going to read them in
86 print. Instead refer to an example input file (@inputfileref), these
87 are clickable in HTML.
89 * Abbrevs in caps, e.g., HTML, DVI, MIDI, etc.
93 0. Do not use a colon to introduce examples, sentences just continue
95 in the display material.
98 2. When beginning a quote: "So, he said,..."
99 This usage is rarer. Americans often just use a comma.
100 3. When adding a defining example at the end of a sentence.
102 * To produce good looking texinfo output (for both TTY and DVI) some
103 additional formatting rules should be followed.
105 . Do not use tabs. They expand to nothing in DVI output.
107 . Do not use spaces at the beginning of a line (except in @example
108 or @verbatim environments), and do not use more than a single space
109 between words. `makeinfo' copies the input lines verbatim without
110 removing those spaces.
112 . Variables or numbers which consist of a single character (probably
113 followed by a punctuation mark) should be tied properly, either to
114 the previous or the next word. Example:
116 The variable@tie{}@var{a} ...
118 . To get consistent indentation in the DVI output it is better to avoid
119 the @verbatim environment. Use the @example environment instead if
120 possible, but without extraneous indentation. For example, this
128 should be replaced with
136 where `@example' starts the line (without leading spaces).
138 . Use the `quote' option in @lilypond commands if possible.
140 . Do not compress the input vertically; this is, do not use
142 Beginning of logical unit
146 continuation of logical unit
150 Beginning of logical unit
157 continuation of logical unit
159 This makes it easier to not forget `@noindent'.
161 . Non-ASCII characters which are in latin-1 should be directly used;
162 this is, don't say `Ba@ss{}tuba' but `Baßtuba'. This ensures that
163 all such characters appear in all output formats.
168 This document is also available in @uref{source/Documentation/user/out-www/lilypond.pdf,PDF}.
173 @documentencoding ISO-8859-1
186 @subtitle The music typesetter
187 @author The LilyPond development team
191 Copyright @copyright{} 1999--2005 by the authors
193 Permission is granted to copy, distribute and/or modify this document
194 under the terms of the GNU Free Documentation License, Version 1.1
195 or any later version published by the Free Software Foundation;
196 with no Invariant Sections.
197 A copy of the license is included in the section entitled ``GNU
198 Free Documentation License''.
202 @c Not yet debugged or reported. This crashes gs-8.01:
203 @c compiling gs-8.01 right now... -- jcn
204 @lilypond[raggedright]
207 \override Score.RehearsalMark #'self-alignment-X = #LEFT
208 \override Score.RehearsalMark #'font-size = #-2
209 \mark #(ly:export (string-append
210 "(For LilyPond version " (lilypond-version) ")"))
224 This file documents GNU LilyPond.
226 Copyright 1999--2005 by the authors
228 Permission is granted to copy, distribute and/or modify this document
229 under the terms of the GNU Free Documentation License, Version 1.1
230 or any later version published by the Free Software Foundation;
231 with no Invariant Sections.
232 A copy of the license is included in the section entitled ``GNU
233 Free Documentation License''.
240 @top GNU LilyPond --- The music typesetter
241 @c HJJ: Info needs `@top', which is a synonym for `@unnumbered' in TeX.
243 This is the user manual for GNU LilyPond 2.6.x series.
245 (See the bottom of this page for the exact version number).
251 A further source of information is the website, which can be found at
252 @uref{http://@/www@/.lilypond@/.org/}. The website contains on-line copies
253 of this and other documentation.
255 @include dedication.itely
259 * Introduction:: What, Why, How.
260 * Tutorial:: A tutorial introduction.
261 * Example templates:: Larger examples.
262 * Putting it all together:: Demonstrates real-life LilyPond usage.
263 * Running LilyPond:: Operation.
264 * Basic notation:: Standard musical notation.
265 * Instrument-specific notation:: Notation that is only used for some
267 * Advanced notation:: Less frequently used notation.
268 * Changing defaults:: Tuning output.
269 * Output formats:: What LilyPond produces.
271 * Interfaces for programmers::
272 * LilyPond-book:: Integrating text and music.
273 * Converting from other formats:: Converting to lilypond source format.
276 * Notation manual details::
279 * GNU Free Documentation License:: FDL.
287 @include macros.itexi
288 @include preface.itely
289 @include introduction.itely
290 @include tutorial.itely
291 @include examples.itely
292 @include putting.itely
293 @include invoking.itely
294 @include basic-notation.itely
295 @include instrument-notation.itely
296 @include advanced-notation.itely
297 @include changing-defaults.itely
298 @include global.itely
300 @include programming-interface.itely
301 @include lilypond-book.itely
302 @include converters.itely
305 @c FIXME: Index has two alphabetically sorted lists @code vs plain?
308 @include literature.itely
309 @include scheme-tutorial.itely
310 @include notation-appendices.itely
311 @include point-and-click.itely
312 @include cheatsheet.itely
316 @appendix LilyPond index