@c -*-texinfo-*-
-@node Tutorial, , , Top
+@c ugh: because of @include, we need to fill in these nodes?
+@node Tutorial
@chapter Tutorial
@menu
* end of tutorial:: The end
@end menu
-@node Introduction, , , Tutorial
+@node Introduction
@section Introduction
LilyPond prints music from a specification that you, the user, supply.
You have to give that specification using a @emph{language}. This
document is a gentle introduction to that language, which is called
-Mudela, an acronym of Music Definition Language.
+Lilypond, an acronym of Music Definition Language.
-This tutorial will demonstrate how to use Mudela by presenting
+This tutorial will demonstrate how to use Lilypond by presenting
examples of input along with resulting output. We will use English
terms for notation. In case you are not familiar with those, you may
consult the glossary that is distributed with LilyPond.
The examples discussed are included in the distribution, in the
subdirectory @file{input/tutorial/}. It is recommended that you
-experiment with writing Mudela input yourself, to get a feel for
+experiment with writing Lilypond input yourself, to get a feel for
how LilyPond behaves.
-@node The first tune, , , Tutorial
+@node The first tune
@section The first tune
full fledged, yet simple example. It is a convoluted version
of the famous menuet in J. S. Bach's @emph{Klavierbuechlein}.
-@mudela[verbatim]
+@lilypond[verbatim]
% lines preceded by a percent are comments which
% are ignored by Lilypond.
\include "paper16.ly"
linewidth = 14.0 \cm;
}
}
-@end mudela
+@end lilypond
Enter it (or copy it, the filename is @file{menuet.ly}), compile it
with LilyPond and view the output. Details of this procedure may vary
\score @{
@end example
- A mudela file combines music with directions for outputting that
+ A lilypond file combines music with directions for outputting that
music. The music is combined with the output directions by putting
them into a @code{\score} block.
@example
the start of a measure. This can help you track down errors.
So far, no notes were chromatically altered. Here is the first one
-that is: @code{fis}. Mudela by default uses Dutch note names, and
+that is: @code{fis}. Lilypond by default uses Dutch note names, and
``Fis'' is the Dutch note name for ``F sharp''. However, there is no
sharp sign in the output. The program keeps track of key signatures,
and will only print accidentals if they are needed.
description. In other words, LilyPond would be best
described by `music compiler' or `music to notation compiler'.
-@node Lyrics and chords, , , Tutorial
+@node Lyrics and chords
@section Lyrics and chords
In this section we show how to typeset a song of unknown
@center @strong{The river is flowing}
@center Traditional
-@mudela[center]
+@lilypond[center]
\header {
title = "The river is flowing";
composer = "Traditional (?)";
\midi { \tempo 4=72;}
\paper { linewidth = 10.0\cm; }
}
-@end mudela
+@end lilypond
Again, we will dissect the file line by line.
@example
@end example
End the score block.
-@node Piano music, , , Tutorial
+@node Piano music
@section Piano music
Our third subject is a piece of piano music. The fragment in the input
file is a piano reduction of the G major Sinfonia by Giovanni Battista
Sammartini. It was composed around 1740.
-@mudela[verbatim]
+@lilypond[verbatim]
\version "1.3.60";
\include "paper16.ly";
\context Voice = oboeTwo {
\stemDown
\grace {
- \property Grace.Stem \push #'direction = #-1
+ \property Grace.Stem \override #'direction = #-1
[f,16 g] }
f8 e e2
} >
indent = 0.0;
linewidth = 15.0 \cm; }
}
-@end mudela
+@end lilypond
If it looks like incomprehensible gibberish to you@dots{} Then you are
right. The author has doctored this example to have as many quirks in
@example
\version "1.3.61";
@end example
-Lilypond and the Mudela language is still under development, therefore
+Lilypond and the Lilypond language is still under development, therefore
it is useful to indicate the Lilypond version of the file. Lilypond
will check the version number and warn you when the syntax has
-changed. Also, the @code{convert-mudela} program will be able to
+changed. Also, the @code{convert-ly} program will be able to
update most of the syntax changes automatically.
@example
viola = \notes \relative c' \context Voice = viola @{
[TODO: demonstrate Hara-Kiri with scores and part extraction.]
-@node end of tutorial, , , Tutorial
+@node end of tutorial
@section The end
That's all folks. From here, you can either try fiddling with input
projects / lilypond.git / blobdiff