This tutorial starts with an introduction to the LilyPond music
language and explains how to produce printed music. After this first
-contact we will explain how to create beautiful printed music
+contact we will explain how to create beautiful printed music
containing common musical notation.
@menu
-* First steps::
-* Single staff notation::
-* Multiple notes at once::
-* Songs::
-* Final touches::
+* First steps::
+* Single staff notation::
+* Multiple notes at once::
+* Songs::
+* Final touches::
@end menu
This section gives a basic introduction to working with LilyPond.
@menu
-* Compiling a file::
-* Simple notation::
+* Compiling a file::
+* Simple notation::
* Working on input files::
* How to read the manual::
@end menu
@seealso
-
Notation Reference: @ruser{Writing pitches},
@ruser{Writing rhythms}, @ruser{Writing rests},
@ruser{Time signature}, @ruser{Clef}.
same output (line-width and all), copy everything from @qq{Start
cut-&-pastable section} to the bottom of the file.
-@seealso
+@seealso
There are more tips for constructing input files in
@ref{Suggestions for writing LilyPond input files}. But it might be
best to read through the rest of the tutorial first.
-
@node Single staff notation
@section Single staff notation
on one staff.
@menu
-* Accidentals and key signatures::
-* Ties and slurs::
-* Articulation and dynamics::
-* Adding text::
-* Automatic and manual beams::
-* Advanced rhythmic commands::
+* Accidentals and key signatures::
+* Ties and slurs::
+* Articulation and dynamics::
+* Adding text::
+* Automatic and manual beams::
+* Advanced rhythmic commands::
@end menu
accidentals can be printed according to different rules, see
@ruser{Automatic accidentals}.
-@seealso
+@seealso
Notation Reference: @ruser{Note names in other languages},
@ruser{Accidentals}, @ruser{Automatic accidentals},
@ruser{Key signature}.
c2~( c8 fis fis4 ~ fis2 g2)
@end lilypond
-@seealso
+@seealso
Notation Reference: @ruser{Ties}, @ruser{Slurs},
@ruser{Phrasing slurs}.
c2\< c2\ff\> c2 c2\!
@end lilypond
-@seealso
+@seealso
Notation Reference: @ruser{Articulations and ornamentations},
@ruser{Fingering instructions}, @ruser{Dynamics}.
@seealso
-
Notation Reference: @ruser{Writing text}.
a8 c b4 d8. c16 b4
@end lilypond
-@seealso
+@seealso
Notation Reference: @ruser{Automatic beams}, @ruser{Manual beams}.
c2 \acciaccatura b16 c2
@end lilypond
-@seealso
+@seealso
Notation Reference: @ruser{Grace notes}, @ruser{Tuplets},
@ruser{Upbeats}.
type of context, one that generates the brace at the left end of
every system and also controls the extent of bar lines.
-@seealso
+@seealso
Notation Reference: @ruser{Keyboard and other multi-staff
instruments},
@ruser{Displaying staves}.
>>
@end lilypond
-@seealso
+@seealso
Notation Reference: @ruser{Simultaneous notes}.
note an @notation{extender line} is usually drawn from the
syllable extending under all the notes for that syllable. It is
entered as two underscores @code{__}. Here is an example from the
-first three bars of @notation{Dido's Lament}, from Purcell's
+first three bars of @notation{Dido's Lament}, from Purcell's
@notation{Dido and Æneas}:
@lilypond[verbatim,quote]
@seealso
-
Notation Reference: @ruser{Vocal music}.
lyrics with variables. These are discussed in @ref{Organizing
pieces with variables}.
-@seealso
+@seealso
Notation Reference: @ruser{Vocal music}.
-
@node Final touches
@section Final touches
If you have not done so already, @emph{please} read @ref{About the
documentation}. There is a lot of information about LilyPond, so
newcomers often do not know where they should look for help. If
-you spend five minutes reading that section carefully, you might
+you spend five minutes reading that section carefully, you might
save yourself hours of frustration looking in the wrong places!