It is also possible to redefine the meaning of @code{|}. This is done
by assigning a music expression to @code{pipeSymbol},
-@lilypond[quote,fragment,raggedright,verbatim]
-pipeSymbol = \bar "||"
+FIXME: example removed to allow doc builds. Needs to be fixed soon. -gp
-{ c'2 c'2 | c'2 c'2 | }
-@end lilypond
+@c @lilypond[quote,fragment,raggedright,verbatim]
+@c pipeSymbol = \bar "||"
+
+@c { c'2 c' | c'2 c }
+@c @end lilypond
@node Skipping corrected music
\time 2/4 c'2 \time 3/4 c'2.
@end lilypond
+@c FIXME: broken numbers for 4/4 and 2/2 time.
The symbol that is printed can be customized with the @code{style}
property. Setting it to @code{#'()} uses fraction style for 4/4 and
2/2 time,
@node Controlling formatting of prefatory matter
@subsection Controlling formatting of prefatory matter
-TODO
+TODO Somebody needs to explain this example, but I don't know what
+they're trying to do, so it won't be me. -gp
+
+TODO part 2, build message: programming error: No spacing entry from KeyCancellation to `key-signature'
@lilypond[verbatim]
\transpose c c' {
@node Polyphony
@section Polyphony
+
+Polyphony in music refers to having more than one voice occuring in
+a piece of music. Polyphony in LilyPond refers to having more than
+one voice on the same staff.
+
+@subsection Writing polyphonic music
+@subsection Writing polyphonic music
@cindex polyphony
The easiest way to enter fragments with more than one voice on a staff
@end lilypond
The separator causes @internalsref{Voice} contexts@footnote{Polyphonic
-voices are sometimes called "layers" in other notation packages}
+voices are sometimes called ``layers'' in other notation packages}
@cindex layers
to be instantiated. They bear the names @code{"1"}, @code{"2"}, etc. In
each of these contexts, vertical direction of slurs, stems, etc. is set
@section Beaming
Beams are used to group short notes into chunks that are aligned with
-the metrum. They are inserted automatically
+the metrum. LilyPond normally inserts beams automatically, but if you
+wish you may control them manually or changed how beams are automatically
+grouped.
+
+@cindex Automatic beams
+@menu
+* Automatic beams::
+* Manual beams::
+* Setting automatic beam behavior::
+* Beam formatting::
+@end menu
+
+@node Automatic beams
+@subsection Automatic beams
+
+LilyPond inserts beams automatically
@lilypond[quote,fragment,verbatim,relative=2]
\time 2/4 c8 c c c \time 6/8 c c c c8. c16 c8
Program reference: @internalsref{Beam}.
-@cindex Automatic beams
-@menu
-* Manual beams::
-* Setting automatic beam behavior::
-* Beam formatting::
-@end menu
-
@node Manual beams
@subsection Manual beams
@cindex beams, manual
@lilypond[quote,fragment,relative=1,verbatim]
{
- f8[ r16 f g a]
- f8[ r16 \set stemLeftBeamCount = #1 f g a]
+ f8[ r16
+ f g a]
+ f8[ r16
+ \set stemLeftBeamCount = #1
+ f g a]
}
@end lilypond
@cindex @code{stemRightBeamCount}
@cindex Frenched staves
Kneed beams are inserted automatically, when a large gap is detected
-between the note heads. This behavior can be tuned through the object
+between the note heads. This behavior can be tuned through the object.
Automatically kneed cross-staff beams cannot be used together with
@code{neutral-direction} property.
-@lilypond
-\relative c'' {
+@lilypond[quote,raggedright,relative=2,fragment,verbatim]
+{
b8[ b]
\override Beam #'neutral-direction = #-1
b[ b]
@b{Supported Clefs} @tab
@b{Example}
+@c FIXME: Unknown clef type `neomensural_c2'
+
@item
modern style mensural C clef @tab
@code{neomensural_c1}, @code{neomensural_c2},
@c cheesy title to avoid clash with chapter name.
-@c FIXME: let's not be so casual about Emacs and VIM, but rather
-@c instruct (how) to use them; let advanced user figure-out what
-@c commands to type?
-
-@c
-@c We don't have enough space to explain either VIM
-@c or Emacs non-advanced users, and I fear that both editors will only
-@c confuse newbies. I vote for keeping the material in footnotes.
-@c
-@c --hwn
-
In the last section we explained what kind of things you could enter
in a LilyPond file. In this section we will explain what commands to
run and how to view or print the output. If you have not used
@c FIXME
@c This is good info, but I wouldn't call it a comment. IMO it should
@c be moved somewhere else. I don't know exactly where yet, but I'll
-@c resolve it soon. -GP
+@c resolve it soon. -gp
@cindex versioning