1 \input texinfo @c -*-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)Invoking LilyPond. Titling LilyPond scores.
21 * GNU LilyPond: (lilypond/lilypond). The GNU music typesetter.
22 * convert-ly: (lilypond/lilypond)Invoking convert-ly. Older LilyPond versions.
23 * midi2ly: (lilypond/lilypond)Invoking midi2ly. Importing MIDI.
24 * etf2ly: (lilypond/lilypond)Invoking etf2ly. Importing Finale.
25 * abc2ly: (lilypond/lilypond)Invoking abc2ly. Importing ABC.
26 * musedata2ly: (lilypond/lilypond)Invoking musedata2ly. Importing MuseData.
27 * mup2ly: (lilypond/lilypond)Invoking mup2ly. Importing Mup.
32 @omfcreator Han-Wen Nienhuys and Jan Nieuwenhuizen
33 @omfdescription User manual of the LilyPond music engraving system
35 @omfcategory Applications|Publishing
39 @c don't remove this comment.
45 * Do not forget to create @cindex entries for new sections of text.
47 * Try not to use punctuation between introductocing sentence and
48 display material (verbatim, music, example code).
50 * Do not refer to LilyPond in the text. The reader knows what the
53 * If you do, capitalization is LilyPond.
55 * Do not explicitly refer to the reader/user. There is no one else
56 besides the reader and the writer.
58 * Do not use abbreviations (don't, won't, etc.).
60 * Avoid fluff (``Notice that,'' ``as you can see,'' ``Currently,'')
62 * Avoid long stretches of input code. Noone is going to read them in
63 print. Instead refer to an example input file (@inputfileref), these
64 are clickable in HTML.
66 * Abbrevs in caps, e.g. HTML, DVI, MIDI, etc.
69 0. Do not use a colon to introduce examples, sentences just continue
71 in the display material.
74 2. When beginning a quote: "So, he said,..."
75 This usage is rarer. Americans often just use a comma.
76 3. When adding a defining example at the end of a sentence.
81 This document is also available in @uref{../lilypond.ps.gz,gzipped
82 PostScript} and @uref{../lilypond.pdf,PDF}.
88 @subtitle The music typesetter
89 @author Han-Wen Nienhuys
90 @author Jan Nieuwenhuizen
91 @author J@"{u}rgen Reuter
96 Copyright @copyright{} 1999--2004 by the authors
98 Permission is granted to copy, distribute and/or modify this document
99 under the terms of the GNU Free Documentation License, Version 1.1
100 or any later version published by the Free Software Foundation;
101 with no Invariant Sections.
102 A copy of the license is included in the section entitled ``GNU
103 Free Documentation License''.
107 @c Not yet debugged or reported. This crashes gs-8.01:
108 @c compiling gs-8.01 right now... -- jcn
109 @lilypond[raggedright]
111 \context Lyrics \notes {
112 \override Score.RehearsalMark #'self-alignment-X = #LEFT
113 \mark #(ly:export (string-append
114 "(For LilyPond version " (lilypond-version) ")"))
128 This file documents GNU LilyPond.
130 Copyright 1999--2004 by the authors
132 Permission is granted to copy, distribute and/or modify this document
133 under the terms of the GNU Free Documentation License, Version 1.1
134 or any later version published by the Free Software Foundation;
135 with no Invariant Sections.
136 A copy of the license is included in the section entitled ``GNU
137 Free Documentation License''.
144 @top GNU LilyPond --- The music typesetter
145 @c HJJ: Info needs `@top', which is a synonym for `@unnumbered' in TeX.
147 This is the user manual for GNU LilyPond 2.3.x series.
149 (See the bottom of this page for the exact version number).
154 A further source of information is the website, which can be found at
155 @uref{http://www.lilypond.org/}. The website contains on-line copies of
156 this and other documentation.
158 @include dedication.itely
162 * Introduction:: What, Why, How.
163 * Tutorial:: A tutorial introduction.
164 * Example templates:: Larger examples
165 * Notation manual:: All notation supported, and how to
167 * Changing defaults:: Tuning output.
168 * Interfaces for programmers::
169 * Invoking LilyPond:: Operation.
170 * Converting from other formats:: Converting to lilypond source format.
171 * lilypond-book manual:: Integrating text and music with lilypond-book.
173 * Notation manual details::
176 * GNU Free Documentation License:: FDL.
183 @include macros.itexi
184 @include preface.itely
185 @include introduction.itely
186 @include tutorial.itely
187 @include examples.itely
188 @include invoking.itexi
189 @include notation.itely
190 @include changing-defaults.itely
191 @include programming-interface.itely
192 @include lilypond-book.itely
193 @include converters.itely
196 @c FIXME: Index has two alphabetically sorted lists @code vs plain?
198 @unnumbered Unified index
202 @include notation-appendices.itely
204 @include literature.itely
206 @include cheatsheet.itely