1 \input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
2 @setfilename lilypond.info
8 @dircategory GNU music project
12 Current version of the manual: 2.8.0
13 ****** Please update this whenever you run convert-ly on the docs.
15 convert-ly --from=... --to=... --no-version *.itely
19 Distributions will want to install lilypond.info in postinstall, doing:
21 install-info --info-dir=/usr/share/info out/lilypond.info
25 * Prepend GNU for dir, must be unique.
27 * Do not list the `lilypond' node at toplevel, so that `info lilypond'
30 * List all commands in direntry.
32 @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.
47 @omfcreator Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
48 @omfdescription User manual of the LilyPond music engraving system
50 @omfcategory Applications|Publishing
54 @c don't remove this comment.
60 * Do not forget to create @cindex entries for new sections of text.
62 * Try not to use punctuation between an introductory sentence and
63 display material (music, example code).
65 * Do not refer to LilyPond in the text. The reader knows what the
66 manual is about. If you do, capitalization is LilyPond.
68 * If you explicitly refer to `lilypond', the program (or any other
69 command to be executed), say `@command{lilypond}'.
71 * Do not explicitly refer to the reader/user. There is no one else
72 besides the reader and the writer.
74 * Do not use abbreviations (don't, won't, etc.). If you do, use a
77 blabla blabla, i.e., blabla blabla
79 * Avoid fluff (``Notice that,'' ``as you can see,'' ``Currently,'').
81 * The above three suggestions refer to the formal Notation Manual
82 (chapters 5 and up). In the Tutorial, Example templates, and
83 Putting it all together, you may write more colloquially
85 * The use of the word `illegal' is inappropriate in most cases. Say
88 * Avoid long stretches of input code. Noone is going to read them in
89 print. Instead refer to an example input file (@inputfileref), these
90 are clickable in HTML.
92 * Abbrevs in caps, e.g., HTML, DVI, MIDI, etc.
96 0. Do not use a colon to introduce examples, sentences just continue
98 in the display material.
100 1. To introduce lists
101 2. When beginning a quote: "So, he said,..."
102 This usage is rarer. Americans often just use a comma.
103 3. When adding a defining example at the end of a sentence.
105 * To produce good looking texinfo output (for both TTY and DVI) some
106 additional formatting rules should be followed.
108 . Do not use tabs. They expand to nothing in DVI output.
110 . Do not use spaces at the beginning of a line (except in @example
111 or @verbatim environments), and do not use more than a single space
112 between words. `makeinfo' copies the input lines verbatim without
113 removing those spaces.
115 . Variables or numbers which consist of a single character (probably
116 followed by a punctuation mark) should be tied properly, either to
117 the previous or the next word. Example:
119 The variable@tie{}@var{a} ...
121 . To get consistent indentation in the DVI output it is better to avoid
122 the @verbatim environment. Use the @example environment instead if
123 possible, but without extraneous indentation. For example, this
131 should be replaced with
139 where `@example' starts the line (without leading spaces).
141 . Use the `quote' option in @lilypond commands if possible.
143 . Do not compress the input vertically; this is, do not use
145 Beginning of logical unit
149 continuation of logical unit
153 Beginning of logical unit
160 continuation of logical unit
162 This makes it easier to not forget `@noindent'.
164 . Non-ASCII characters which are in utf-8 should be directly used;
165 this is, don't say `Ba@ss{}tuba' but `Baßtuba'. This ensures that
166 all such characters appear in all output formats.
171 This document is also available in @uref{source/Documentation/user/lilypond.pdf,PDF}.
176 @documentencoding utf-8
189 @subtitle The music typesetter
190 @author The LilyPond development team
194 Copyright @copyright{} 1999--2006 by the authors
196 Permission is granted to copy, distribute and/or modify this document
197 under the terms of the GNU Free Documentation License, Version 1.1
198 or any later version published by the Free Software Foundation;
199 with no Invariant Sections.
200 A copy of the license is included in the section entitled ``GNU
201 Free Documentation License''.
205 @c Not yet debugged or reported. This crashes gs-8.01:
206 @c compiling gs-8.01 right now... -- jcn
207 @lilypond[ragged-right]
210 \override Score.RehearsalMark #'self-alignment-X = #LEFT
211 \override Score.RehearsalMark #'font-size = #-2
212 \mark #(ly:export (string-append
213 "(For LilyPond version " (lilypond-version) ")"))
227 This file documents GNU LilyPond.
229 Copyright 1999--2006 by the authors
231 Permission is granted to copy, distribute and/or modify this document
232 under the terms of the GNU Free Documentation License, Version 1.1
233 or any later version published by the Free Software Foundation;
234 with no Invariant Sections.
235 A copy of the license is included in the section entitled ``GNU
236 Free Documentation License''.
243 @top GNU LilyPond --- The music typesetter
244 @c HJJ: Info needs `@top', which is a synonym for `@unnumbered' in TeX.
246 This is the user manual for GNU LilyPond 2.8.x series.
248 (See the bottom of this page for the exact version number).
254 A further source of information is the website, which can be found at
255 @uref{http://@/www@/.lilypond@/.org/}. The website contains on-line copies
256 of this and other documentation.
258 @include dedication.itely
262 * Introduction:: What, Why, How.
263 * Tutorial:: A tutorial introduction.
264 * Example templates:: Larger examples.
265 * Working on LilyPond projects:: Demonstrates real-life LilyPond usage.
266 * Running LilyPond:: Operation.
267 * Basic notation:: Standard musical notation.
268 * Instrument-specific notation:: Notation that is only used for some
270 * Advanced notation:: Less frequently used notation.
271 * Changing defaults:: Tuning output.
272 * Global issues:: What LilyPond produces.
274 * Interfaces for programmers::
275 * LilyPond-book:: Integrating text and music.
276 * Converting from other formats:: Converting to lilypond source format.
279 * Notation manual details::
282 * GNU Free Documentation License:: FDL.
290 @include macros.itexi
291 @include preface.itely
292 @include introduction.itely
293 @include tutorial.itely
294 @include examples.itely
295 @include putting.itely
296 @include invoking.itely
297 @include basic-notation.itely
298 @include instrument-notation.itely
299 @include advanced-notation.itely
300 @include changing-defaults.itely
301 @include global.itely
303 @include programming-interface.itely
304 @include lilypond-book.itely
305 @include converters.itely
308 @c FIXME: Index has two alphabetically sorted lists @code vs plain?
311 @include literature.itely
312 @include scheme-tutorial.itely
313 @include notation-appendices.itely
314 @include point-and-click.itely
315 @include cheatsheet.itely
319 @appendix LilyPond index