1 @c -*- coding: utf-8; mode: texinfo; -*-
2 @c This file is part of lilypond-learning.tely
4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. See TRANSLATION for details.
15 This chapter introduces readers to LilyPond and the
20 * About the documentation::
27 This section covers the overall goals and architecture of
32 * Automated engraving::
33 * What symbols to engrave?::
34 * Music representation::
35 * Example applications::
42 The art of music typography is called @emph{(plate) engraving}. The
43 term derives from the traditional process of music printing. Just a
44 few decades ago, sheet music was made by cutting and stamping the
45 music into a zinc or pewter plate in mirror image. The plate would be
46 inked, the depressions caused by the cutting and stamping would hold
47 ink. An image was formed by pressing paper to the plate. The
48 stamping and cutting was completely done by hand. Making a correction
49 was cumbersome, if possible at all, so the engraving had to be perfect
50 in one go. Engraving was a highly specialized skill; a craftsman had
51 to complete around five years of training before earning the title of
52 master engraver, and another five years of experience were
53 necessary to become truly skilled.
55 Nowadays, all newly printed music is produced with computers. This
56 has obvious advantages; prints are cheaper to make, and editorial work
57 can be delivered by email. Unfortunately, the pervasive use of
58 computers has also decreased the graphical quality of scores.
59 Computer printouts have a bland, mechanical look, which makes them
60 unpleasant to play from.
63 @c introduce illustrating aspects of engraving, font...
64 The images below illustrate the difference between traditional
65 engraving and typical computer output, and the third picture shows how
66 LilyPond mimics the traditional look. The left picture shows a scan
67 of a flat symbol from an edition published in 2000. The center
68 depicts a symbol from a hand-engraved Bärenreiter edition of the
69 same music. The left scan illustrates typical flaws of computer
70 print: the staff lines are thin, the weight of the flat symbol matches
71 the light lines and it has a straight layout with sharp corners. By
72 contrast, the Bärenreiter flat has a bold, almost voluptuous
73 rounded look. Our flat symbol is designed after, among others, this
74 one. It is rounded, and its weight harmonizes with the thickness of
75 our staff lines, which are also much thicker than lines in the
78 @multitable @columnfractions .125 .25 .25 .25 .125
82 @image{henle-flat-gray,,4cm}
85 @image{henle-flat-gray,,,png}
90 @image{baer-flat-gray,,4cm}
93 @image{baer-flat-gray,,,png}
98 @image{lily-flat-bw,,4cm}
101 @image{lily-flat-bw,,,png}
105 @image{lilypond/henle-flat-bw,,,png} @image{lilypond/baer-flat-bw,,,png}
106 @image{lilypond/lily-flat-bw,,,png}
114 LilyPond Feta font (2003)
119 @cindex musical symbols
124 @c introduce illustrating aspects of engraving, spacing...
125 In spacing, the distribution of space should reflect the durations
126 between notes. However, many modern scores adhere to the durations
127 with mathematical precision, which leads to poor results. In the next
128 example a motive is printed twice: once using exact mathematical
129 spacing, and once with corrections. Can you spot which fragment is
132 @cindex optical spacing
133 @c file spacing-optical.
134 @c need to include it here, because we want two images.
155 \override NoteSpacing #'stem-spacing-correction = #0.6
180 \override NoteSpacing #'stem-spacing-correction = #0.0
181 \override NoteSpacing #'same-direction-correction = #0.0
182 \override StaffSpacing #'stem-spacing-correction = #0.0
188 @cindex regular rhythms
189 @cindex regular spacing
191 Each bar in the fragment only uses notes that are played in a constant
192 rhythm. The spacing should reflect that. Unfortunately, the eye
193 deceives us a little; not only does it notice the distance between
194 note heads, it also takes into account the distance between
195 consecutive stems. As a result, the notes of an up-stem/@/down-stem
196 combination should be put farther apart, and the notes of a
197 down-stem/@/up-stem combination should be put closer together, all
198 depending on the combined vertical positions of the notes. The upper
199 two measures are printed with this correction, the lower two measures
200 without, forming down-stem/@/up-stem clumps of notes.
204 Musicians are usually more absorbed with performing than with studying
205 the looks of a piece of music, so nitpicking about typographical
206 details may seem academical. But it is not. In larger pieces with
207 monotonous rhythms, spacing corrections lead to subtle variations in
208 the layout of every line, giving each one a distinct visual signature.
209 Without this signature all lines would look the same, and they become
210 like a labyrinth. If a musician looks away once or has a lapse in
211 concentration, the lines might lose their place on the page.
213 Similarly, the strong visual look of bold symbols on heavy staff lines
214 stands out better when the music is far away from the reader, for
215 example, if it is on a music stand. A careful distribution of white
216 space allows music to be set very tightly without cluttering symbols
217 together. The result minimizes the number of page turns, which is a
220 This is a common characteristic of typography. Layout should be
221 pretty, not only for its own sake, but especially because it helps the
222 reader in her task. For performance material like sheet music, this
223 is of double importance: musicians have a limited amount of attention.
224 The less attention they need for reading, the more they can focus on
225 playing the music. In other words, better typography translates to
228 These examples demonstrate that music typography is an art that is
229 subtle and complex, and that producing it requires considerable
230 expertise, which musicians usually do not have. LilyPond is our
231 effort to bring the graphical excellence of hand-engraved music to the
232 computer age, and make it available to normal musicians. We have
233 tuned our algorithms, font-designs, and program settings to produce
234 prints that match the quality of the old editions we love to see and
240 @node Automated engraving
241 @subsection Automated engraving
243 How do we go about implementing typography? If craftsmen need over
244 ten years to become true masters, how could we simple hackers ever
245 write a program to take over their jobs?
247 The answer is: we cannot. Typography relies on human judgment of
248 appearance, so people cannot be replaced completely. However, much of
249 the dull work can be automated. If LilyPond solves most of the common
250 situations correctly, this will be a huge improvement over existing
251 software. The remaining cases can be tuned by hand. Over the course
252 of years, the software can be refined to do more and more things
253 automatically, so manual overrides are less and less necessary.
255 When we started, we wrote the LilyPond program entirely in the C++
256 programming language; the program's functionality was set in stone by
257 the developers. That proved to be unsatisfactory for a number of
261 @item When LilyPond makes mistakes,
262 users need to override formatting decisions. Therefore, the user must
263 have access to the formatting engine. Hence, rules and settings cannot
264 be fixed by us at compile-time but must be accessible for users at
267 @item Engraving is a matter of visual judgment, and therefore a matter of
268 taste. As knowledgeable as we are, users can disagree with our
269 personal decisions. Therefore, the definitions of typographical style
270 must also be accessible to the user.
272 @item Finally, we continually refine the formatting algorithms, so we
273 need a flexible approach to rules. The C++ language forces a certain
274 method of grouping rules that do not match well with how music
278 These problems have been addressed by integrating an interpreter for
279 the Scheme programming language and rewriting parts of LilyPond in
280 Scheme. The current formatting architecture is built around the
281 notion of graphical objects, described by Scheme variables and
282 functions. This architecture encompasses formatting rules,
283 typographical style and individual formatting decisions. The user has
284 direct access to most of these controls.
286 Scheme variables control layout decisions. For example, many
287 graphical objects have a direction variable that encodes the choice
288 between up and down (or left and right). Here you see two chords,
289 with accents and arpeggios. In the first chord, the graphical objects
290 have all directions down (or left). The second chord has all
291 directions up (right).
293 @lilypond[quote,ragged-right]
295 \override SpacingSpanner #'spacing-increment = #3
296 \override TimeSignature #'transparent = ##t
298 \stemDown <e g b>4_>-\arpeggio
299 \override Arpeggio #'direction = #RIGHT
300 \stemUp <e g b>4^>-\arpeggio
305 The process of formatting a score consists of reading and writing the
306 variables of graphical objects. Some variables have a preset value. For
307 example, the thickness of many lines -- a characteristic of typographical
308 style -- is a variable with a preset value. You are free to alter this
309 value, giving your score a different typographical impression.
311 @lilypond[quote,ragged-right]
314 c'4-~ c'16 as g f e16 g bes c' des'4
319 \override Beam #'thickness = #0.3
320 \override Stem #'thickness = #0.5
321 \override Bar #'thickness = #3.6
322 \override Tie #'thickness = #2.2
323 \override StaffSymbol #'thickness = #3.0
324 \override Tie #'extra-offset = #'(0 . 0.3)
330 Formatting rules are also preset variables: each object has variables
331 containing procedures. These procedures perform the actual
332 formatting, and by substituting different ones, we can change the
333 appearance of objects. In the following example, the rule which note
334 head objects are used to produce their symbol is changed during the
337 @lilypond[quote,ragged-right]
338 #(set-global-staff-size 30)
340 #(define (mc-squared grob orig current)
341 (let* ((interfaces (ly:grob-interfaces grob))
342 (pos (ly:grob-property grob 'staff-position)))
343 (if (memq 'note-head-interface interfaces)
345 (ly:grob-set-property! grob 'stencil ly:text-interface::print)
346 (ly:grob-set-property! grob 'font-family 'roman)
347 (ly:grob-set-property! grob 'text
348 (make-raise-markup -0.5
350 ((-5) (make-simple-markup "m"))
351 ((-3) (make-simple-markup "c "))
352 ((-2) (make-smaller-markup (make-bold-markup "2")))
353 (else (make-simple-markup "bla")))))))))
355 \new Voice \relative c' {
357 \set autoBeaming = ##f
360 \once \override NoteHead #'stencil = #ly:note-head::brew-ez-stencil
361 \once \override NoteHead #'font-size = #-7
362 \once \override NoteHead #'font-family = #'sans
363 \once \override NoteHead #'font-series = #'bold
365 \once \override NoteHead #'style = #'cross
367 \applyOutput #'Voice #mc-squared
370 { d8[ es-( fis^^ g] fis2-) }
371 \repeat unfold 5 { \applyOutput #'Voice #mc-squared s8 }
378 @node What symbols to engrave?
379 @subsection What symbols to engrave?
384 The formatting process decides where to place symbols. However, this
385 can only be done once it is decided @emph{what} symbols should be
386 printed, in other words what notation to use.
388 Common music notation is a system of recording music that has evolved
389 over the past 1000 years. The form that is now in common use dates
390 from the early renaissance. Although the basic form (i.e., note heads
391 on a 5-line staff) has not changed, the details still evolve to
392 express the innovations of contemporary notation. Hence, it
393 encompasses some 500 years of music. Its applications range from
394 monophonic melodies to monstrous counterpoints for large orchestras.
396 How can we get a grip on such a many-headed beast, and force it into
397 the confines of a computer program? Our solution is to break up the
398 problem of notation (as opposed to engraving, i.e., typography) into
399 digestible and programmable chunks: every type of symbol is handled by
400 a separate module, a so-called plug-in. Each plug-in is completely
401 modular and independent, so each can be developed and improved
402 separately. Such plug-ins are called @code{engraver}s, by analogy
403 with craftsmen who translate musical ideas to graphic symbols.
405 In the following example, we see how we start out with a plug-in for
406 note heads, the @code{Note_heads_engraver}.
408 @lilypond[quote,ragged-right]
409 \include "engraver-example.ily"
416 \remove "Stem_engraver"
417 \remove "Phrasing_slur_engraver"
418 \remove "Slur_engraver"
419 \remove "Script_engraver"
420 \remove "Beam_engraver"
421 \remove "Auto_beam_engraver"
425 \remove "Accidental_engraver"
426 \remove "Key_engraver"
427 \remove "Clef_engraver"
428 \remove "Bar_engraver"
429 \remove "Time_signature_engraver"
430 \remove "Staff_symbol_engraver"
431 \consists "Pitch_squash_engraver"
438 Then a @code{Staff_symbol_engraver} adds the staff
440 @lilypond[quote,ragged-right]
441 \include "engraver-example.ily"
448 \remove "Stem_engraver"
449 \remove "Phrasing_slur_engraver"
450 \remove "Slur_engraver"
451 \remove "Script_engraver"
452 \remove "Beam_engraver"
453 \remove "Auto_beam_engraver"
457 \remove "Accidental_engraver"
458 \remove "Key_engraver"
459 \remove "Clef_engraver"
460 \remove "Bar_engraver"
461 \consists "Pitch_squash_engraver"
462 \remove "Time_signature_engraver"
469 the @code{Clef_engraver} defines a reference point for the staff
471 @lilypond[quote,ragged-right]
472 \include "engraver-example.ily"
479 \remove "Stem_engraver"
480 \remove "Phrasing_slur_engraver"
481 \remove "Slur_engraver"
482 \remove "Script_engraver"
483 \remove "Beam_engraver"
484 \remove "Auto_beam_engraver"
488 \remove "Accidental_engraver"
489 \remove "Key_engraver"
490 \remove "Bar_engraver"
491 \remove "Time_signature_engraver"
498 and the @code{Stem_engraver} adds stems.
500 @lilypond[quote,ragged-right]
501 \include "engraver-example.ily"
508 \remove "Phrasing_slur_engraver"
509 \remove "Slur_engraver"
510 \remove "Script_engraver"
511 \remove "Beam_engraver"
512 \remove "Auto_beam_engraver"
516 \remove "Accidental_engraver"
517 \remove "Key_engraver"
518 \remove "Bar_engraver"
519 \remove "Time_signature_engraver"
526 The @code{Stem_engraver} is notified of any note head coming along.
527 Every time one (or more, for a chord) note head is seen, a stem
528 object is created and connected to the note head. By adding
529 engravers for beams, slurs, accents, accidentals, bar lines,
530 time signature, and key signature, we get a complete piece of
533 @lilypond[quote,ragged-right]
534 \include "engraver-example.ily"
538 This system works well for monophonic music, but what about
539 polyphony? In polyphonic notation, many voices can share a staff.
541 @lilypond[quote,ragged-right]
542 \include "engraver-example.ily"
543 \new Staff << \topVoice \\ \botVoice >>
546 In this situation, the accidentals and staff are shared, but the stems,
547 slurs, beams, etc., are private to each voice. Hence, engravers should
548 be grouped. The engravers for note heads, stems, slurs, etc., go into a
549 group called @q{Voice context,} while the engravers for key, accidental,
550 bar, etc., go into a group called @q{Staff context.} In the case of
551 polyphony, a single Staff context contains more than one Voice context.
552 Similarly, multiple Staff contexts can be put into a single Score
553 context. The Score context is the top level notation context.
557 Internals Reference: @rinternals{Contexts}.
559 @lilypond[quote,ragged-right]
560 \include "engraver-example.ily"
563 \new Staff << \topVoice \\ \botVoice >>
564 \new Staff << \pah \\ \hoom >>
569 @node Music representation
570 @subsection Music representation
572 Ideally, the input format for any high-level formatting system is an
573 abstract description of the content. In this case, that would be the
574 music itself. This poses a formidable problem: how can we define what
575 music really is? Instead of trying to find an answer, we have reversed
576 the question. We write a program capable of producing sheet music,
577 and adjust the format to be as lean as possible. When the format can
578 no longer be trimmed down, by definition we are left with content
579 itself. Our program serves as a formal definition of a music
582 The syntax is also the user-interface for LilyPond, hence it is easy
592 a quarter note C1 (middle C) and an eighth note D1 (D above middle C)
600 On a microscopic scale, such syntax is easy to use. On a larger
601 scale, syntax also needs structure. How else can you enter complex
602 pieces like symphonies and operas? The structure is formed by the
603 concept of music expressions: by combining small fragments of music
604 into larger ones, more complex music can be expressed. For example
606 @lilypond[quote,verbatim,fragment,relative=1]
611 Chords can be constructed with @code{<<} and @code{>>} enclosing the notes
613 @c < > is not a music expression,
614 @c so we use <<>> iso. <> to drive home the point of
615 @c expressions. Don't change this back --hwn.
620 @lilypond[quote,fragment,relative=1]
621 \new Voice { <<c4 d4 e>> }
625 This expression is put in sequence by enclosing it in curly braces
626 @code{@{@tie{}@dots{}@tie{}@}}
629 @{ f4 <<c4 d4 e4>> @}
632 @lilypond[quote,relative=1,fragment]
637 The above is also an expression, and so it may be combined
638 again with another simultaneous expression (a half note) using <<,
642 << g2 \\ @{ f4 <<c4 d4 e4>> @} >>
645 @lilypond[quote,fragment,relative=2]
646 \new Voice { << g2 \\ { f4 <<c d e>> } >> }
649 Such recursive structures can be specified neatly and formally in a
650 context-free grammar. The parsing code is also generated from this
651 grammar. In other words, the syntax of LilyPond is clearly and
652 unambiguously defined.
654 User-interfaces and syntax are what people see and deal with
655 most. They are partly a matter of taste, and also subject of much
656 discussion. Although discussions on taste do have their merit, they
657 are not very productive. In the larger picture of LilyPond, the
658 importance of input syntax is small: inventing neat syntax is easy, while
659 writing decent formatting code is much harder. This is also
660 illustrated by the line-counts for the respective components: parsing
661 and representation take up less than 10% of the source code.
664 @node Example applications
665 @subsection Example applications
667 We have written LilyPond as an experiment of how to condense the art
668 of music engraving into a computer program. Thanks to all that hard
669 work, the program can now be used to perform useful tasks. The
670 simplest application is printing notes.
672 @lilypond[quote,relative=1]
680 By adding chord names and lyrics we obtain a lead sheet.
682 @lilypond[quote,ragged-right]
684 \chords { c2 c f2 c }
685 \new Staff \relative c' { \time 2/4 c4 c g'4 g a4 a g2 }
686 \new Lyrics \lyricmode { twin4 kle twin kle lit tle star2 }
690 Polyphonic notation and piano music can also be printed. The following
691 example combines some more exotic constructs.
693 @lilypondfile[quote,ragged-right]{screech-boink.ly}
695 The fragments shown above have all been written by hand, but that is
696 not a requirement. Since the formatting engine is mostly automatic, it
697 can serve as an output means for other programs that manipulate
698 music. For example, it can also be used to convert databases of
699 musical fragments to images for use on websites and multimedia
702 This manual also shows an application: the input format is text, and
703 can therefore be easily embedded in other text-based formats such as
704 @LaTeX{}, HTML, or in the case of this manual, Texinfo. By means of a
705 special program, the input fragments can be replaced by music images
706 in the resulting PDF or HTML output files. This makes it easy
707 to mix music and text in documents.
710 @node About the documentation
711 @section About the documentation
713 This section explains the different manuals:
717 Learning Manual (LM): this introduces LilyPond, giving in-depth
718 explanations of how to create notation.
721 Music Glossary (MG): this explains musical terms and gives
722 translations of terms in other languages.
725 Notation Reference (NR): this is the @q{main} portion of the
726 documentation. It provides detailed information about creating
730 Application Usage (AU): this discusses the actual programs and
731 operation system-specific issues.
734 Snippet List (SL): this is a collection of useful snippets from
736 @uref{http://lsr@/.dsi@/.unimi@/.it,LilyPond Snippet Repository},
737 a public-domain collection of LilyPond examples.
740 Other documentation: there are a few other portions of the
741 documentation, such as News items and the mailist archives.
746 * About the Learning Manual (LM)::
747 * About the Music Glossary (MG)::
748 * About the Notation Reference (NR)::
749 * About the Application Usage (AU)::
750 * About the Snippet List (SL)::
751 * Other documentation::
755 @node About the Learning Manual (LM)
756 @subsection About the Learning Manual (LM)
759 @node About the Music Glossary (MG)
760 @subsection About the Music Glossary (MG)
762 @node About the Notation Reference (NR)
763 @subsection About the Notation Reference (NR)
765 @node About the Application Usage (AU)
766 @subsection About the Application Usage (AU)
769 @node About the Snippet List (SL)
770 @subsection About the Snippet List (SL)
773 @node Other documentation
774 @subsection Other documentation
777 FIXME: needs almost-complete rewrite. -gp
779 There are four manuals about LilyPond: the @emph{Learning Manual},
780 the @emph{Notation Reference}, the @emph{Application Usage}, and the
781 @emph{Internals Reference}.
784 @subheading Learning Manual (LM)
786 This book explains how to begin learning LilyPond, as well as explaining
787 some key concepts in easy terms. It is recommended to read these
788 chapters in a linear fashion.
796 @emph{@ref{Tutorial}},
797 gives a gentle introduction to typesetting music. First time
798 users should start here.
801 @emph{@ref{Fundamental concepts}},
802 explains some general concepts about the LilyPond file format. If
803 you are not certain where to place a command, read this chapter!
806 @emph{@ref{Working on LilyPond projects}},
807 discusses practical uses of LilyPond and how to avoid some common
811 @emph{@ref{Tweaking output}},
812 shows how to change the default engraving that LilyPond
818 @subheading Notation Reference (NR)
820 This book explains all the LilyPond commands which produce notation. It
821 assumes that readers are familiar with the concepts in the Learning
824 All of this needs to be rewritten after GDP, anyway.
831 @emph{@r ef{Basic notation}},
832 discusses topics grouped by notation construct. This section gives
833 details about basic notation that will be useful in almost any
837 @emph{@r ef{Instrument-specific notation}},
838 discusses topics grouped by notation construct. This section gives
839 details about special notation that will only be useful for particular
840 instrument (or vocal) groups.
843 @emph{@r ef{Advanced notation}},
844 discusses topics grouped by notation construct. This section gives
845 details about complicated or unusual notation.
848 @emph{@r ef{Changing defaults}},
849 explains how to fine tune layout.
852 @emph{@r ef{Non-musical notation}},
853 discusses non-musical output such as titles, multiple movements,
854 and how to select which MIDI instruments to use.
857 @emph{@r ef{Spacing issues}},
858 discusses issues which affect the global output, such as selecting
859 paper size or specifying page breaks.
862 @emph{@r ef{Interfaces for programmers}},
863 explains how to create music functions.
868 @subsubheading Appendices
870 This book contains useful reference charts.
877 @emph{@r ef{Literature list}},
878 contains a set of useful reference books for those who wish to know
879 more on notation and engraving.
883 @emph{@r ef{Scheme tutorial}},
884 presents a short introduction to Scheme, the programming
885 language that music functions use.
888 @emph{@r ef{Notation manual tables}},
889 are a set of tables showing the chord names, MIDI instruments,
890 a list of color names, and the Feta font.
893 @emph{@r ef{Templates}},
894 of LilyPond pieces. Just cut and paste a
895 template into a file, add notes, and you're done!
899 @emph{@r ef{Cheat sheet}},
900 is a handy reference of the most common LilyPond commands.
904 @emph{@r ef{LilyPond command index}},
905 is an index of all LilyPond @code{\commands}.
909 @emph{@r ef{LilyPond index}},
917 @subheading Program usage
919 This book explains how to execute the program and how to integrate
920 LilyPond notation with other programs.
925 @emph{@rprogram{Install}},
926 explains how to install LilyPond (including compilation if desired).
929 @emph{@rprogram{Setup}},
930 describes how to configure your computer for optimum LilyPond usage,
931 such as using special environments for certain text editors.
934 @emph{@rprogram{Running LilyPond}},
935 shows how to run LilyPond and its helper programs. In addition, this
936 section explains how to upgrade input files from previous versions of
940 @emph{@rprogram{LilyPond-book}},
941 explains the details behind creating
942 documents with in-line music examples, like this manual.
945 @emph{@rprogram{Converting from other formats}},
946 explains how to run the conversion programs. These programs are
947 supplied with the LilyPond package, and convert a variety of music
948 formats to the @code{.ly} format.
954 @subsubheading Other information
956 There are a number of other places which may be very valuable.
962 @cindex foreign languages
966 The @ref{Top,Music glossary,,music-glossary}, explains musical terms and
967 includes translations to various languages. It is also available in
971 The music glossary explains musical terms, and includes translations
972 to various languages. It is a separate document, available in HTML
975 If you are not familiar with music notation or music terminology
976 (especially if you are a non-native English speaker), it is highly
977 advisable to consult the glossary.
984 @uref{source/input/lsr/lilypond-snippets/index.html,Snippets}
989 are a great collection of short examples which demonstrate tricks, tips,
990 and special features of LilyPond. Most of these snippets can also be
991 found in the @uref{http://lsr.dsi.unimi.it/,LilyPond Snippet
992 Repository}. This website also has a searchable LilyPond manual.
1001 @ref{Top,Internals Reference,,lilypond-internals}
1003 is a set of heavily cross linked HTML pages, which document the
1004 nitty-gritty details of each and every LilyPond class, object, and
1005 function. It is produced directly from the formatting definitions used.
1007 Almost all formatting functionality that is used internally, is
1008 available directly to the user. For example, all variables that control
1009 thickness values, distances, etc., can be changed in input files. There
1010 are a huge number of formatting options, and all of them are described
1011 in this document. Each section of the notation manual has a @b{See
1012 also} subsection, which refers to the generated documentation. In the
1013 HTML document, these subsections have clickable links.
1018 Once you are an experienced user, you can use the manual as reference:
1019 there is an extensive index@footnote{If you are looking for something,
1020 and you cannot find it in the manual, that is considered a bug. In
1021 that case, please file a bug report.}, but the document is also
1027 @uref{source/Documentation/user/lilypond-big-page.html, one big page},
1029 which can be searched easily using the search facility of a web
1033 In all HTML documents that have music fragments embedded, the LilyPond
1034 input that was used to produce that image can be viewed by clicking
1037 The location of the documentation files that are mentioned here can vary
1038 from system to system. On occasion, this manual refers to
1039 initialization and example files. Throughout this manual, we refer to
1040 input files relative to the top-directory of the source archive. For
1041 example, @file{input/@/lsr/@/dirname/@/bla@/.ly} may refer to the file
1042 @file{lilypond@/2.x.y/@/input/@/lsr/@/dirname/@/bla@/.ly}. On binary
1043 packages for the UNIX platform, the documentation and examples can
1044 typically be found somewhere below
1045 @file{/usr/@/share/@/doc/@/lilypond/}. Initialization files, for
1046 example @file{scm/@/lily@/.scm}, or @file{ly/@/engraver@/-init@/.ly},
1047 are usually found in the directory @file{/usr/@/share/@/lilypond/}.
1049 @cindex adjusting output
1052 @cindex lilypond-internals
1053 @cindex internal documentation
1055 @cindex extending LilyPond
1058 Finally, this and all other manuals, are available online both as PDF
1059 files and HTML from the web site, which can be found at
1060 @uref{http://@/www@/.lilypond@/.org/}.