version that you are working on. See TRANSLATION for details.
@end ignore
-@c \version "2.11.61"
+@c \version "2.12.0"
@node Keyboard and other multi-staff instruments
@section Keyboard and other multi-staff instruments
@subsection Common notation for keyboards
This section discusses notation issues that may arise for most
-many-stringed instruments.
+keyboard instruments.
@menu
* References for keyboards::
@end itemize
+@c @snippets
+@c @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@c {forcing-visibility-of-systems-with-multi-bar-rests-when-using-\RemoveEmptyStaffContext.ly}
+@c http://lsr.dsi.unimi.it/LSR/Item?u=1&id=312
@seealso
Learning Manual:
@var{staffname}. Typical values for @var{staffname} are
@code{"up"} and @code{"down"}, or @code{"RH"} and @code{"LH"}.
+The staff to which the voice is being switched must exist at the
+time of the switch. If necessary, staves should be @qq{kept alive},
+see @ref{Keeping contexts alive}.
+
Cross-staff notes are beamed automatically:
@lilypond[verbatim,quote]
Notation Reference:
@ref{Stems},
-@ref{Automatic beams}.
+@ref{Automatic beams},
+@ref{Keeping contexts alive}.
Snippets:
@rlsr{Keyboards}.
If additional control is needed over the individual staves, they
can be created manually with the names @code{"up"} and
@code{"down"}. The @code{\autochange} command will then switch
-its voice between the existing staves. For example, this is
-necessary to place a key signature in the lower staff:
+its voice between the existing staves.
+
+@warning{If staves are created manually, they @emph{must} be named
+@code{"up"} and @code{"down"}.}
+
+For example, staves must be created manually in order to place a
+key signature in the lower staff:
@lilypond[quote,verbatim]
\new PianoStaff <<
The placement of the pedal commands matches the physical movement of the
sustain pedal during piano performance. Pedalling to the final bar line
-is indicated by omitting the final pedal up command.
+is indicated by omitting the final pedal off command.
@seealso
@node Harp
@subsection Harp
+This section discusses notation issues that are unique to the harp.
+
@menu
-* Harp notation::
+* References for harps::
* Harp pedals::
@end menu
-@node Harp notation
-@unnumberedsubsubsec Harp notation
+@node References for harps
+@unnumberedsubsubsec References for harps
+@cindex harps
+@cindex bisbiglando
-TBC
+Some common characteristics of harp music are covered elsewhere:
-@ignore
-Some possibilities:
-- glissandi
-- tremolo (for bisbigliando)
-- natural harmonics
-- directional arpeggio and non-arpeggio
-- workaroung for keeping both staves visible in an orchestral
- score,
-http://lists.gnu.org/archive/html/lilypond-user/2007-08/msg00386.html
-and http://lsr.dsi.unimi.it/LSR/Item?u=1&id=312
-
-An LSR snippet could be used to demonstrate the main items; in the
-case of glissandi, it would be desirable to have a demonstration
-of different styles.
-@end ignore
+@itemize
+
+@item The glissando is the most characterisic harp technique,
+@ref{Glissando}.
+
+@item A @notation{bisbigliando} is written as a tremelo @ref{Tremolo
+repeats}
+
+@item Natural harmonics are covered under @ref{Harmonics}.
+
+@item For directional arpeggios and non-arpeggios, see @ref{Arpeggio}.
+
+@end itemize
+
+@seealso
+Notation Reference:
+@ref{Tremolo repeats}
+@ref{Glissando}
+@ref{Arpeggio}
+@ref{Harmonics}
@node Harp pedals
@unnumberedsubsubsec Harp pedals
@seealso
Notation Reference:
-@ruser{Text scripts}
+@ref{Text scripts}
+@ref{Instrument Specific Markup}