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
17 @c prepend GNU for dir, must be unique
18 @c do not list the `lilypond' node at toplevel, so that `info lilypond'
20 @c * lilypond: (lilypond/lilypond)Running LilyPond. Invoking the
22 * GNU LilyPond: (lilypond/lilypond). The GNU music typesetter.
23 * convert-ly: (lilypond/lilypond)Invoking convert-ly. Older LilyPond versions.
24 * midi2ly: (lilypond/lilypond)Invoking midi2ly. Importing MIDI.
25 * etf2ly: (lilypond/lilypond)Invoking etf2ly. Importing Finale.
26 * abc2ly: (lilypond/lilypond)Invoking abc2ly. Importing ABC.
27 * musedata2ly: (lilypond/lilypond)Invoking musedata2ly. Importing MuseData.
28 * mup2ly: (lilypond/lilypond)Invoking mup2ly. Importing Mup.
33 @omfcreator Han-Wen Nienhuys and Jan Nieuwenhuizen
34 @omfdescription User manual of the LilyPond music engraving system
36 @omfcategory Applications|Publishing
40 @c don't remove this comment.
46 * Do not forget to create @cindex entries for new sections of text.
48 * Try not to use punctuation between introductocing sentence and
49 display material (verbatim, music, example code).
51 * Do not refer to LilyPond in the text. The reader knows what the
54 * If you do, capitalization is LilyPond.
56 * Do not explicitly refer to the reader/user. There is no one else
57 besides the reader and the writer.
59 * Do not use abbreviations (don't, won't, etc.).
61 * Avoid fluff (``Notice that,'' ``as you can see,'' ``Currently,'')
63 * Avoid long stretches of input code. Noone is going to read them in
64 print. Instead refer to an example input file (@inputfileref), these
65 are clickable in HTML.
67 * Abbrevs in caps, e.g. HTML, DVI, MIDI, etc.
70 0. Do not use a colon to introduce examples, sentences just continue
72 in the display material.
75 2. When beginning a quote: "So, he said,..."
76 This usage is rarer. Americans often just use a comma.
77 3. When adding a defining example at the end of a sentence.
82 This document is also available in @uref{../lilypond.ps.gz,gzipped
83 PostScript} and @uref{../lilypond.pdf,PDF}.
88 @documentencoding ISO-8859-1
101 @subtitle The music typesetter
102 @author The LilyPond development team
106 Copyright @copyright{} 1999--2004 by the authors
108 Permission is granted to copy, distribute and/or modify this document
109 under the terms of the GNU Free Documentation License, Version 1.1
110 or any later version published by the Free Software Foundation;
111 with no Invariant Sections.
112 A copy of the license is included in the section entitled ``GNU
113 Free Documentation License''.
117 @c Not yet debugged or reported. This crashes gs-8.01:
118 @c compiling gs-8.01 right now... -- jcn
119 @lilypond[raggedright]
122 \override Score.RehearsalMark #'self-alignment-X = #LEFT
123 \override Score.RehearsalMark #'font-size = #-2
124 \mark #(ly:export (string-append
125 "(For LilyPond version " (lilypond-version) ")"))
139 This file documents GNU LilyPond.
141 Copyright 1999--2004 by the authors
143 Permission is granted to copy, distribute and/or modify this document
144 under the terms of the GNU Free Documentation License, Version 1.1
145 or any later version published by the Free Software Foundation;
146 with no Invariant Sections.
147 A copy of the license is included in the section entitled ``GNU
148 Free Documentation License''.
155 @top GNU LilyPond --- The music typesetter
156 @c HJJ: Info needs `@top', which is a synonym for `@unnumbered' in TeX.
158 This is the user manual for GNU LilyPond 2.3.x series.
160 (See the bottom of this page for the exact version number).
165 A further source of information is the website, which can be found at
166 @uref{http://@/www@/.lilypond@/.org/}. The website contains on-line copies
167 of this and other documentation.
169 @include dedication.itely
173 * Introduction:: What, Why, How.
174 * Tutorial:: A tutorial introduction.
175 * Example templates:: Larger examples
176 * Notation manual:: All notation supported, and how to
178 * Sound:: Producing MIDI output
179 * Changing defaults:: Tuning output.
180 * Interfaces for programmers::
181 * Running LilyPond:: Operation.
182 * Converting from other formats:: Converting to lilypond source format.
183 * Integrating text and music:: Integrating text and music with lilypond-book.
186 * Notation manual details::
189 * GNU Free Documentation License:: FDL.
197 @include macros.itexi
198 @include preface.itely
199 @include introduction.itely
200 @include tutorial.itely
201 @include examples.itely
202 @include invoking.itely
203 @include notation.itely
204 @include sound-output.itexi
205 @include changing-defaults.itely
206 @include programming-interface.itely
207 @include lilypond-book.itely
208 @include converters.itely
211 @c FIXME: Index has two alphabetically sorted lists @code vs plain?
214 @include literature.itely
215 @include scheme-tutorial.itely
216 @include notation-appendices.itely
217 @include point-and-click.itely
220 @appendix Unified index
226 @include cheatsheet.itely