what LilyPond has done to the file. If any errors occur, please
examine this file.
-@subsubheading Unix
+@subsubheading UNIX
Create a text file called @file{test.ly} and enter:
works in practice. Starting from a B, which is on the middle line
in a treble clef, you can reach a C, D and E within 3 staff spaces
going up, and an A, G and F within 3 staff spaces going down. So
-if the note following a B is a C, D or F it will be assumed to be
+if the note following a B is a C, D or E it will be assumed to be
above the B, and an A, G or F will be assumed to be below.
@lilypond[verbatim,quote,ragged-right]
little) space there is at the beginning of a line, but indenting
LilyPond code like this makes it much easier for humans to read.
-@c FIXME: number of backslashes?! works in html but not pdf.
@warning{each note is relative to the previous note in
the input, not relative to the @code{c''} in the initial
-@code{\\relative} command.}
+@code{@bs{}relative} command.}
@subheading Simultaneous music expressions: single staff
Time signatures entered in one staff affects all other staves by
default. On the other hand, the key signature of one staff does
-@emph{not} affect other staves. This different default behaviour
+@emph{not} affect other staves. This different default behavior
is because scores with transposing instruments are more common
than polyrhythmic scores.
was used to write the file:
@example
-\version "2.11.38"
+\version @w{"@version{}"}
@end example
@noindent
underneath the @ref{Version number}.
@example
-\version "2.11.38"
+\version @w{"@version{}"}
\header @{
title = "Symphony"
composer = "Me"