version that you are working on. See TRANSLATION for details.
@end ignore
-@c \version "2.11.38"
+@c \version "2.11.51"
@ignore
Tutorial guidelines: (different from policy.txt!)
or
@lilypond[verbatim,quote,relative=2]
- Don't use any other relative=X commands (make it a non-fragment
- example), and don't use fragment without relative=2.
+ Don't use any other relative=X commands.
- use "aes" and "ees" instead of "as" and "es". I know it's not
correct Dutch naming, but let's not confuse people with this
until we get to the Basic notation chapter.
-- Add "Music Glossary: @rglos{foo}" to the _top_ of the relevant
+- Add "Music Glossary: @rglos{foo}" to the *top* of the relevant
portions of the tutorial.
@end ignore
@example
lilypond test.ly
-GNU LilyPond 2.12.0
+GNU LilyPond @version{}
Processing `test.ly'
Parsing...
Interpreting music...
is within just one staff space of the previous note.
@lilypond[verbatim,quote]
-\relative c' { % set the starting point to middle C
+% set the starting point to middle C
+\relative c' {
c d e f
g a b c
}
octave:
@lilypond[verbatim,quote]
-\relative c'' { % one octave above middle C
+% one octave above middle C
+\relative c'' {
e c a c
}
@end lilypond
c4 c g' g a a g2
%@{
- This line, and the notes below
- are ignored, since they are in a
- block comment.
+ This line, and the notes below are ignored,
+ since they are in a block comment.
- g g f f e e d d c2
+ f f e e d d c2
%@}
@end example
@w{@code{\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
+displayed input, but you @strong{must} add the
@w{@code{\relative c'' @{ @}}} like this:
@example
@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.
Music Glossary: @rglos{fingering}.
-
Similarly, @notation{fingering} indications can be added to a note
using a dash (@code{-}) and the digit to be printed:
extended section of music, use the command @code{\autoBeamOff}
to turn off automatic beaming and @code{\autoBeamOn} to turn it
on again.
-@c It will usually be necessary to manually beam music
-@c with lyrics.
@lilypond[verbatim,quote,relative=2]
\autoBeamOff
Here is an example showing this and everything we have learned so
far about aligning lyrics to notes.
-@c FIXME: noragged-right
-@lilypond[verbatim,quote]
+@c no ragged-right here because otherwise the hyphens get lost,
+@c but the example is long enough to avoid looking strange.
+@lilypond[verbatim,quote,noragged-right]
<<
\relative c' {
\key g \major
@c no ragged-right here because otherwise the hyphens get lost,
@c but the example is long enough to avoid looking strange.
-@c FIXME: noragged-right
-@lilypond[verbatim,quote]
+@lilypond[verbatim,quote,noragged-right]
<<
\relative c' {
\clef bass
placing lyrics under more than one staff. Here is an
example from Handel's @notation{Judas Maccabæus}:
-@c TODO \partial has not been previously explained
-@c Change example or add explanation earlier
-
@lilypond[verbatim,quote]
<<
- {
- \time 6/8
- \partial 8
- }
\relative c'' {
\key f \major
+ \time 6/8
+ \partial 8
c8 c([ bes]) a a([ g]) f f'4. b, c4.~ c4
}
\addlyrics {
}
\relative c' {
\key f \major
+ \time 6/8
+ \partial 8
r8 r4. r4 c8 a'([ g]) f f([ e]) d e([ d]) c bes'4
}
\addlyrics {
>>
@end lilypond
-@noindent
-but scores any more complex than this simple example are
-better produced by separating out the staff structure
-from the notes and lyrics with variables. These are
-discussed in @ref{Organizing pieces with variables}.
+Scores any more complex than this simple example are better
+produced by separating out the score structure from the notes and
+lyrics with variables. These are discussed in @ref{Organizing
+pieces with variables}.
@seealso
(@code{\namedMusic}, just like a normal LilyPond command).
@lilypond[verbatim,quote]
-violin = \new Staff { \relative c'' {
- a4 b c b
-}}
-cello = \new Staff { \relative c {
- \clef bass
- e2 d
-}}
+violin = \new Staff {
+ \relative c'' {
+ a4 b c b
+ }
+}
+cello = \new Staff {
+ \relative c {
+ \clef bass
+ e2 d
+ }
+}
{
<<
\violin
\aFivePaper
line-width = \width
@}
-@{ c4^\name @}
+@{
+ c4^\name
+@}
@end example
These annotations make future upgrades of LilyPond go more
smoothly. Changes in the syntax are handled with a special
-program, @file{convert-ly}, and it uses @code{\version} to
+program, @command{convert-ly}, and it uses @code{\version} to
determine what rules to apply. For details, see
@rprogram{Updating files with convert-ly}.
The title, composer, opus number, and similar information are
entered in the @code{\header} block. This exists outside of the
main music expression; the @code{\header} block is usually placed
-underneath the @ref{Version number}.
+underneath the version number.
@example
\version @w{"@version{}"}
@node After the tutorial
@subsection After the tutorial
-FIXME: rewrite slightly after the rest of the LM has been
-stabilized. Translators, ignore this section for now.
-
After finishing the tutorial, you should probably try writing a
piece or two. Start by adding notes to one of the
@ref{Templates}. If you need any notation that was not covered in
wish to skim these chapters right now, and come back to them after
you have more experience.
-
-
+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
+save yourself hours of frustration looking in the wrong places!
projects / lilypond.git / blobdiff