1 \input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
2 @setfilename lilypond.info
8 @dircategory GNU music project
13 Current version of the manual: 2.6.0
14 Please update this whenever you run convert-ly on the docs.
16 convert-ly --from=... --to=... --no-version *.itely
20 Distributions will want to install lilypond.info in postinstall, doing:
22 install-info --info-dir=/usr/share/info out/lilypond.info
26 * Prepend GNU for dir, must be unique.
28 * Do not list the `lilypond' node at toplevel, so that `info lilypond'
31 * List all commands in direntry.
33 @c * lilypond: (lilypond/lilypond)Running LilyPond. Invoking the
38 * LilyPond: (lilypond/lilypond). The GNU music typesetter.
39 * abc2ly: (lilypond/lilypond)Invoking abc2ly. Importing ABC.
40 * convert-ly: (lilypond/lilypond)Invoking convert-ly. Older LilyPond versions.
41 * etf2ly: (lilypond/lilypond)Invoking etf2ly. Importing Finale.
42 * lilypond-book: (lilypond/lilypond)LilyPond-book. Itegrating text and music.
43 * midi2ly: (lilypond/lilypond)Invoking midi2ly. Importing MIDI.
44 * mup2ly: (lilypond/lilypond)Invoking mup2ly. Importing Mup.
45 * musedata2ly: (lilypond/lilypond)Invoking musedata2ly. Importing MuseData.
50 @omfcreator Han-Wen Nienhuys and Jan Nieuwenhuizen
51 @omfdescription User manual of the LilyPond music engraving system
53 @omfcategory Applications|Publishing
57 @c don't remove this comment.
63 * Do not forget to create @cindex entries for new sections of text.
65 * Try not to use punctuation between an introductory sentence and
66 display material (music, example code).
68 * Do not refer to LilyPond in the text. The reader knows what the
69 manual is about. If you do, capitalization is LilyPond.
71 * If you explicitly refer to `lilypond', the program (or any other
72 command to be executed), say `@command{lilypond}'.
74 * Do not explicitly refer to the reader/user. There is no one else
75 besides the reader and the writer.
77 * Do not use abbreviations (don't, won't, etc.). If you do, use a
80 blabla blabla, i.e., blabla blabla
82 * Avoid fluff (``Notice that,'' ``as you can see,'' ``Currently,'').
84 * The above three suggestions refer to the formal Notation Manual
85 (chapters 5 and up). In the Tutorial, Example templates, and
86 Putting it all together, you may write more colloquially
88 * The use of the word `illegal' is inappropriate in most cases. Say
91 * Avoid long stretches of input code. Noone is going to read them in
92 print. Instead refer to an example input file (@inputfileref), these
93 are clickable in HTML.
95 * Abbrevs in caps, e.g., HTML, DVI, MIDI, etc.
99 0. Do not use a colon to introduce examples, sentences just continue
101 in the display material.
103 1. To introduce lists
104 2. When beginning a quote: "So, he said,..."
105 This usage is rarer. Americans often just use a comma.
106 3. When adding a defining example at the end of a sentence.
108 * To produce good looking texinfo output (for both TTY and DVI) some
109 additional formatting rules should be followed.
111 . Do not use tabs. They expand to nothing in DVI output.
113 . Do not use spaces at the beginning of a line (except in @example
114 or @verbatim environments), and do not use more than a single space
115 between words. `makeinfo' copies the input lines verbatim without
116 removing those spaces.
118 . Variables or numbers which consist of a single character (probably
119 followed by a punctuation mark) should be tied properly, either to
120 the previous or the next word. Example:
122 The variable@tie{}@var{a} ...
124 . To get consistent indentation in the DVI output it is better to avoid
125 the @verbatim environment. Use the @example environment instead if
126 possible, but without extraneous indentation. For example, this
134 should be replaced with
142 where `@example' starts the line (without leading spaces).
144 . Use the `quote' option in @lilypond commands if possible.
146 . Do not compress the input vertically; this is, do not use
148 Beginning of logical unit
152 continuation of logical unit
156 Beginning of logical unit
163 continuation of logical unit
165 This makes it easier to not forget `@noindent'.
167 . Non-ASCII characters which are in utf-8 should be directly used;
168 this is, don't say `Ba@ss{}tuba' but `Baßtuba'. This ensures that
169 all such characters appear in all output formats.
174 This document is also available in @uref{source/Documentation/user/out-www/lilypond.pdf,PDF}.
179 @documentencoding utf-8
192 @subtitle The music typesetter
193 @author The LilyPond development team
197 Copyright @copyright{} 1999--2005 by the authors
199 Permission is granted to copy, distribute and/or modify this document
200 under the terms of the GNU Free Documentation License, Version 1.1
201 or any later version published by the Free Software Foundation;
202 with no Invariant Sections.
203 A copy of the license is included in the section entitled ``GNU
204 Free Documentation License''.
208 @c Not yet debugged or reported. This crashes gs-8.01:
209 @c compiling gs-8.01 right now... -- jcn
210 @lilypond[raggedright]
213 \override Score.RehearsalMark #'self-alignment-X = #LEFT
214 \override Score.RehearsalMark #'font-size = #-2
215 \mark #(ly:export (string-append
216 "(For LilyPond version " (lilypond-version) ")"))
230 This file documents GNU LilyPond.
232 Copyright 1999--2005 by the authors
234 Permission is granted to copy, distribute and/or modify this document
235 under the terms of the GNU Free Documentation License, Version 1.1
236 or any later version published by the Free Software Foundation;
237 with no Invariant Sections.
238 A copy of the license is included in the section entitled ``GNU
239 Free Documentation License''.
246 @top GNU LilyPond --- The music typesetter
247 @c HJJ: Info needs `@top', which is a synonym for `@unnumbered' in TeX.
249 This is the user manual for GNU LilyPond 2.6.x series.
251 (See the bottom of this page for the exact version number).
257 A further source of information is the website, which can be found at
258 @uref{http://@/www@/.lilypond@/.org/}. The website contains on-line copies
259 of this and other documentation.
261 @include dedication.itely
265 * Introduction:: What, Why, How.
266 * Tutorial:: A tutorial introduction.
267 * Example templates:: Larger examples.
268 * Putting it all together:: Demonstrates real-life LilyPond usage.
269 * Running LilyPond:: Operation.
270 * Basic notation:: Standard musical notation.
271 * Instrument-specific notation:: Notation that is only used for some
273 * Advanced notation:: Less frequently used notation.
274 * Changing defaults:: Tuning output.
275 * Output formats:: What LilyPond produces.
277 * Interfaces for programmers::
278 * LilyPond-book:: Integrating text and music.
279 * Converting from other formats:: Converting to lilypond source format.
282 * Notation manual details::
285 * GNU Free Documentation License:: FDL.
293 @include macros.itexi
294 @include preface.itely
295 @include introduction.itely
296 @include tutorial.itely
297 @include examples.itely
298 @include putting.itely
299 @include invoking.itely
300 @include basic-notation.itely
301 @include instrument-notation.itely
302 @include advanced-notation.itely
303 @include changing-defaults.itely
304 @include global.itely
306 @include programming-interface.itely
307 @include lilypond-book.itely
308 @include converters.itely
311 @c FIXME: Index has two alphabetically sorted lists @code vs plain?
314 @include literature.itely
315 @include scheme-tutorial.itely
316 @include notation-appendices.itely
317 @include point-and-click.itely
318 @include cheatsheet.itely
322 @appendix LilyPond index