X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fuser%2Ftutorial.itely;h=f5c20df99596a69f176c9bff63a8d43a6b426417;hb=b97565a9af1c13369ac7e7e9ea80c2638dbc0e51;hp=816dc6136c4fbc2badf3061cc4ee8cde80703b88;hpb=ddf4ac73ac35388f57c59913606066f1b602ca02;p=lilypond.git diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index 816dc6136c..f5c20df995 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -7,7 +7,7 @@ version that you are working on. See TRANSLATION for details. @end ignore -@c \version "2.11.51" +@c \version "2.12.0" @ignore Tutorial guidelines: (different from policy.txt!) @@ -33,15 +33,15 @@ Tutorial guidelines: (different from policy.txt!) 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 @@ -51,8 +51,8 @@ containing common musical notation. 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 @@ -275,7 +275,7 @@ example, the first note -- the @code{d} -- is the closest D to middle C. By adding (or removing) quotes @code{'} or commas @code{,} from -the @w{@code{\relative c' @{}} command, we can change the starting +the @code{@w{\relative c' @{}} command, we can change the starting octave: @lilypond[verbatim,quote] @@ -326,7 +326,7 @@ comma @code{,} to the note name. To change a note by two (or more!) octaves, we use multiple @code{''} or @code{,,} -- but be careful that you use two single quotes @code{''} and not one double quote @code{"}@tie{}! The -initial value in @w{@code{\relative c'}} may also be modified like +initial value in @code{@w{\relative c'}} may also be modified like this. @c " - keeps quotes in order for context-sensitive editor -td @@ -460,7 +460,6 @@ Here is a small example showing all these elements together: @seealso - Notation Reference: @ruser{Writing pitches}, @ruser{Writing rhythms}, @ruser{Writing rests}, @ruser{Time signature}, @ruser{Clef}. @@ -504,7 +503,7 @@ Notes are lower case: @w{@code{@{ c d e @}}} is valid input; @item @strong{Whitespace insensitive}: -it does not matter how many spaces (or new lines) you add. +it does not matter how many spaces (or tabs or new lines) you add. @w{@code{@{ c d e @}}} means the same thing as @w{@code{@{ c @tie{}} @tie{} @tie{} d e @}} and: @@ -523,6 +522,13 @@ thumb is to indent code blocks with either a tab or two spaces: @} @end example +However, whitespace @emph{is} required to separate many syntactical +elements from others. In other words, whitespace can always be +@emph{added}, but it cannot be @emph{eliminated}. As missing +whitespace can give rise to strange errors it is advisable to +always insert whitespace before and after every syntactic element, +for example, before and after every curly brace. + @item @strong{Expressions}: every piece of LilyPond input needs to have @strong{@{ curly @@ -591,11 +597,11 @@ comments: @cindex files, tips for constructing LilyPond input must be surrounded by @{ @} marks or a -@w{@code{\relative c'' @{ ... @}}}, as we saw in @ref{Working on +@code{@w{\relative c'' @{ ... @}}}, as we saw in @ref{Working on input files}. For the rest of this manual, most examples will omit this. To replicate the examples, you may copy and paste the displayed input, but you @strong{must} add the -@w{@code{\relative c'' @{ @}}} like this: +@code{@w{\relative c'' @{ @}}} like this: @example \relative c'' @{ @@ -605,9 +611,9 @@ displayed input, but you @strong{must} add the Why omit the braces? Most examples in this manual can be inserted into the middle of a longer piece of music. For these examples, -it does not make sense to add @w{@code{\relative c'' @{ @}}} -- +it does not make sense to add @code{@w{\relative c'' @{ @}}} -- you should not place a @code{\relative} inside another -@code{\relative}! If we included @w{@code{\relative c'' @{ @}}} +@code{\relative}! If we included @code{@w{\relative c'' @{ @}}} around every example, you would not be able to copy a small documentation example and paste it inside a longer piece of your own. Most people want to add material to an existing piece, so we @@ -634,14 +640,13 @@ you have a starting template for experiments. To see exactly the 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 @@ -649,12 +654,12 @@ This section introduces common notation that is used for one voice 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 @@ -758,14 +763,14 @@ d cis fis No note has a printed accidental, but you must still add @code{is} and type @code{cis} and @code{fis} in the input file. -The code @code{e} does not mean @qq{print a black dot just on -the first line of the staff.} Rather, it means @qq{there is a -note with pitch E-natural.} In the key of A-flat major, it +The code @code{b} does not mean @qq{print a black dot just on +the middle line of the staff.} Rather, it means @qq{there is a +note with pitch B-natural.} In the key of A-flat major, it @emph{does} get an accidental: @lilypond[verbatim,quote,relative=2] \key aes \major -e +b @end lilypond Adding all alterations explicitly might require a little more @@ -775,8 +780,8 @@ according to different conventions. For some examples how 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}. @@ -852,8 +857,8 @@ larger groups of notes. Slurs and ties can be nested. c2~( c8 fis fis4 ~ fis2 g2) @end lilypond -@seealso +@seealso Notation Reference: @ruser{Ties}, @ruser{Slurs}, @ruser{Phrasing slurs}. @@ -942,8 +947,8 @@ example @code{\f}, will end the (de)crescendo, or the command c2\< c2\ff\> c2 c2\! @end lilypond -@seealso +@seealso Notation Reference: @ruser{Articulations and ornamentations}, @ruser{Fingering instructions}, @ruser{Dynamics}. @@ -975,7 +980,6 @@ a1_\markup{ @seealso - Notation Reference: @ruser{Writing text}. @@ -1025,8 +1029,8 @@ a8 c b4 d8. c16 b4 a8 c b4 d8. c16 b4 @end lilypond -@seealso +@seealso Notation Reference: @ruser{Automatic beams}, @ruser{Manual beams}. @@ -1102,8 +1106,8 @@ c2 \appoggiatura b16 c2 c2 \acciaccatura b16 c2 @end lilypond -@seealso +@seealso Notation Reference: @ruser{Grace notes}, @ruser{Tuplets}, @ruser{Upbeats}. @@ -1366,9 +1370,10 @@ suitable for vocal scores. These staff groups each form another type of context, one that generates the brace at the left end of every system and also controls the extent of bar lines. -@seealso -Notation Reference: @ruser{Keyboard instruments}, +@seealso +Notation Reference: @ruser{Keyboard and other multi-staff +instruments}, @ruser{Displaying staves}. @@ -1422,57 +1427,16 @@ r4 8( \> 4 \!) @funindex \\ @funindex >> -When different melodic lines are combined on a single staff they -are printed as polyphonic voices; each voice has its own stems, -slurs and beams, and the top voice has the stems up, while the -bottom voice has them down. - -Entering such parts is done by entering each voice as a sequence -(with @w{@code{@{...@}}}) and combining these simultaneously, -separating the voices with @code{\\}: - -@lilypond[verbatim,quote,relative=2] -<< - { a4 g2 f4~ f4 } \\ - { r4 g4 f2 f4 } ->> -@end lilypond - -For polyphonic music typesetting, spacer rests can also be -convenient; these are rests that do not print. They are useful -for filling up voices that temporarily do not play. Here is the -same example with a spacer rest (@code{s}) instead of a normal -rest (@code{r}), - -@lilypond[verbatim,quote,relative=2] -<< - { a4 g2 f4~ f4 } \\ - { s4 g4 f2 f4 } ->> -@end lilypond - -@noindent -Again, these expressions can be nested arbitrarily. - -@lilypond[verbatim,quote,relative=2] -<< - \new Staff << - { a4 g2 f4~ f4 } \\ - { s4 g4 f2 f4 } - >> - \new Staff << - \clef bass - { 1 ~ 4 } \\ - { e,,4 d e2 ~ e4} - >> ->> -@end lilypond +Polyphonic music in lilypond, while not difficult, uses concepts +that we haven't discussed yet, so we're not going to introduce +them here. Instead, the following sections introduce these concepts +and explain them thoroughly. @seealso +Learning Manual: @ref{Voices contain music}. Notation Reference: @ruser{Simultaneous notes}. - @node Songs @section Songs @@ -1627,7 +1591,7 @@ If a syllable extends over several notes or a single very long 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] @@ -1696,7 +1660,6 @@ Here's an example from Rossini's @notation{Figaro}, where @seealso - Notation Reference: @ruser{Vocal music}. @@ -1738,12 +1701,11 @@ produced by separating out the score structure from the notes and 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 @@ -2028,6 +1990,6 @@ cross-references for further reading. 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!