1 \input texinfo @c -*- coding: latin-1; mode: texinfo; -*-
2 @setfilename lilypond.info
9 Distributions will want to install lilypond.info in postinstall, doing:
11 install-info --info-dir=/usr/share/info out/lilypond.info
15 @dircategory GNU music project
19 * Prepend GNU for dir, must be unique.
21 * Do not list the `lilypond' node at toplevel, so that `info lilypond'
24 * List all commands in direntry.
26 @c * lilypond: (lilypond/lilypond)Running LilyPond. Invoking the
31 * LilyPond: (lilypond/lilypond). The GNU music typesetter.
32 * abc2ly: (lilypond/lilypond)Invoking abc2ly. Importing ABC.
33 * convert-ly: (lilypond/lilypond)Invoking convert-ly. Older LilyPond versions.
34 * etf2ly: (lilypond/lilypond)Invoking etf2ly. Importing Finale.
35 * lilypond-book: (lilypond/lilypond)LilyPond-book. Itegrating text and music.
36 * midi2ly: (lilypond/lilypond)Invoking midi2ly. Importing MIDI.
37 * mup2ly: (lilypond/lilypond)Invoking mup2ly. Importing Mup.
38 * musedata2ly: (lilypond/lilypond)Invoking musedata2ly. Importing MuseData.
43 @omfcreator Han-Wen Nienhuys and Jan Nieuwenhuizen
44 @omfdescription User manual of the LilyPond music engraving system
46 @omfcategory Applications|Publishing
50 @c don't remove this comment.
56 * Do not forget to create @cindex entries for new sections of text.
58 * Try not to use punctuation between an introductory sentence and
59 display material (music, example code).
61 * Do not refer to LilyPond in the text. The reader knows what the
62 manual is about. If you do, capitalization is LilyPond.
64 * If you explicitly refer to `lilypond', the program (or any other
65 command to be executed), say `@command{lilypond}'.
67 * Do not explicitly refer to the reader/user. There is no one else
68 besides the reader and the writer.
70 * Do not use abbreviations (don't, won't, etc.). If you do, use a
73 blabla blabla, i.e., blabla blabla
75 * Avoid fluff (``Notice that,'' ``as you can see,'' ``Currently,'').
77 * The use of the word `illegal' is inappropriate in most cases. Say
80 * Avoid long stretches of input code. Noone is going to read them in
81 print. Instead refer to an example input file (@inputfileref), these
82 are clickable in HTML.
84 * Abbrevs in caps, e.g., HTML, DVI, MIDI, etc.
88 0. Do not use a colon to introduce examples, sentences just continue
90 in the display material.
93 2. When beginning a quote: "So, he said,..."
94 This usage is rarer. Americans often just use a comma.
95 3. When adding a defining example at the end of a sentence.
97 * To produce good looking texinfo output (for both TTY and DVI) some
98 additional formatting rules should be followed.
100 . Do not use tabs. They expand to nothing in DVI output.
102 . Do not use spaces at the beginning of a line (except in @example
103 or @verbatim environments), and do not use more than a single space
104 between words. `makeinfo' copies the input lines verbatim without
105 removing those spaces.
107 . Variables or numbers which consist of a single character (probably
108 followed by a punctuation mark) should be tied properly, either to
109 the previous or the next word. Example:
111 The variable@tie{}@var{a} ...
113 . To get consistent indentation in the DVI output it is better to avoid
114 the @verbatim environment. Use the @example environment instead if
115 possible, but without extraneous indentation. For example, this
123 should be replaced with
131 where `@example' starts the line (without leading spaces).
133 . Use the `quote' option in @lilypond commands if possible.
135 . Do not compress the input vertically; this is, do not use
137 Beginning of logical unit
141 continuation of logical unit
145 Beginning of logical unit
152 continuation of logical unit
154 This makes it easier to not forget `@noindent'.
156 . Non-ASCII characters which are in latin-1 should be directly used;
157 this is, don't say `Ba@ss{}tuba' but `Baßtuba'. This ensures that
158 all such characters appear in all output formats.
163 This document is also available in @uref{../lilypond.ps.gz,gzipped
164 PostScript} and @uref{../lilypond.pdf,PDF}.
169 @documentencoding ISO-8859-1
182 @subtitle The music typesetter
183 @author The LilyPond development team
187 Copyright @copyright{} 1999--2005 by the authors
189 Permission is granted to copy, distribute and/or modify this document
190 under the terms of the GNU Free Documentation License, Version 1.1
191 or any later version published by the Free Software Foundation;
192 with no Invariant Sections.
193 A copy of the license is included in the section entitled ``GNU
194 Free Documentation License''.
198 @c Not yet debugged or reported. This crashes gs-8.01:
199 @c compiling gs-8.01 right now... -- jcn
200 @lilypond[raggedright]
203 \override Score.RehearsalMark #'self-alignment-X = #LEFT
204 \override Score.RehearsalMark #'font-size = #-2
205 \mark #(ly:export (string-append
206 "(For LilyPond version " (lilypond-version) ")"))
220 This file documents GNU LilyPond.
222 Copyright 1999--2005 by the authors
224 Permission is granted to copy, distribute and/or modify this document
225 under the terms of the GNU Free Documentation License, Version 1.1
226 or any later version published by the Free Software Foundation;
227 with no Invariant Sections.
228 A copy of the license is included in the section entitled ``GNU
229 Free Documentation License''.
236 @top GNU LilyPond --- The music typesetter
237 @c HJJ: Info needs `@top', which is a synonym for `@unnumbered' in TeX.
239 This is the user manual for GNU LilyPond 2.5.x series.
241 (See the bottom of this page for the exact version number).
246 A further source of information is the website, which can be found at
247 @uref{http://@/www@/.lilypond@/.org/}. The website contains on-line copies
248 of this and other documentation.
250 @include dedication.itely
254 * Introduction:: What, Why, How.
255 * Tutorial:: A tutorial introduction.
256 * Example templates:: Larger examples.
257 * Basic notation:: Standard musical notation.
258 * Instrument-specific notation:: Notation that is only used for some
260 * Advanced notation:: Less frequently used notation.
261 * Global issues:: Non-notation commands.
263 * Notation manual:: All notation supported, and how to
264 produce it. (SOON OBSOLETE)
265 * Sound:: Producing MIDI output (SOON OBSOLETE)
267 * Changing defaults:: Tuning output.
268 * Interfaces for programmers::
269 * Running LilyPond:: Operation.
270 * Converting from other formats:: Converting to lilypond source format.
271 * LilyPond-book:: Integrating text and music.
274 * Notation manual details::
276 * GNU Free Documentation License:: FDL.
285 @include macros.itexi
286 @include preface.itely
287 @include introduction.itely
288 @include tutorial.itely
289 @include examples.itely
290 @include invoking.itely
291 @include basic-notation.itely
292 @include instrument-notation.itely
293 @include advanced-notation.itely
294 @include global.itely
296 @include notation.itely
297 @include sound-output.itexi
299 @include changing-defaults.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 Unified index