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!)
@example
lilypond test.ly
-GNU LilyPond 2.12.0
+GNU LilyPond @version{}
Processing `test.ly'
Parsing...
Interpreting music...
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.
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