@@lilypond[verbatim,quote,relative=2]
@end example
-If using any combination of @code{\header@{@}}, @code{\score@{@}} or
-@code{\layout@{@}} in your example, then you must omit the
-@code{relative} variable and either use absolute entry mode or an
-explicit @code{\relative@{@}} construction.
-
-If using @code{\book@{@}} in your example then you must also omit the
-@code{relative} variable and either use absolute entry mode or an
-explicit @code{\relative@{@}} construction. However, you must also
+If using @code{\book@{@}} in your example then you must also
include the @code{papersize=X} variable, where @code{X} is a defined
paper size from within @file{scm/paper.scm}. This is to avoid the
default @code{a4} paper size being used and leaving too much unnecessary
@cindex pitches, absolute values
@cindex absolute note names
-So far we have always used @code{\relative} to define pitches.
+So far we have used @code{\relative} to define pitches.
This is usually the fastest way to enter most music. Without
@code{\relative}, pitches are interpreted in absolute mode.
In this mode, LilyPond treats all pitches as absolute values. A
-@code{c'} will always mean middle C, a @code{b} will always mean
-the note one step below middle C, and a @code{g,} will always mean
+@code{c'} will always mean middle@tie{}C, a @code{b} will always mean
+the note one step below middle@tie{}C, and a @code{g,} will always mean
the note on the bottom staff of the bass clef.
@lilypond[verbatim,quote]
@rglos{scale}, @rglos{middle C}, @rglos{octave},
@rglos{accidental}.
+LilyPond uses lower-case letters for pitches. The letters
+@code{c} through@tie{}@code{b} denote pitches in the
+@q{small octave} below @notation{middle C}. Added @code{'}
+or@tie{}@code{,} suffixes indicate higher or lower octaves.
+Here is a scale starting on @notation{middle C}, and an arpeggio:
+
+@lilypond[verbatim,quote]
+{ c' d' e' f' g' a' b' c'' g c' e' g' c'' e'' g'' c''' }
+@end lilypond
+
The easiest way to enter notes is by using @code{\relative} mode.
In this mode, the octave is chosen automatically by assuming the
following note is always to be placed closest to the previous
@}
@end example
-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
-@q{@w{@code{@bs{}relative c'' @{ @dots{} @}}}} -- you should not
-place a @code{\relative} inside another @code{\relative}! If we
-included @q{@w{@code{@bs{}relative c'' @{ @dots{} @}}}} 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 format the
-manual this way.
-
Also, remember that every LilyPond file should have a
@code{\version} statement. Because the examples in the manuals
are snippets, not files, the @code{\version} statement is omitted.
door @emph{muziekuitdrukkingen}. Een enkele noot is een
muziekuitdrukking:
-@lilypond[verbatim,quote,relative=2] a4
+@lilypond[verbatim,quote,fragment]
+a'4
@end lilypond
Een noot tussen accolades zetten maakt er een