X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fuser%2Fexpressive.itely;h=d8d000c7280d67aec63a57e25277009a3c8e4faf;hb=c10e42d15b978acf35c75671b16c618215be8215;hp=514a2d8cc2cf82fe0e780cd409713d8dd03c9087;hpb=92eb006cff3771c5f76058de84ae9e0ad9e74eb4;p=lilypond.git

diff --git a/Documentation/user/expressive.itely b/Documentation/user/expressive.itely
index 514a2d8cc2..d8d000c728 100644
--- a/Documentation/user/expressive.itely
+++ b/Documentation/user/expressive.itely
@@ -6,11 +6,16 @@
     version that you are working on.  See TRANSLATION for details.
 @end ignore
 
+@c \version "2.11.51"
+
 @node Expressive marks
 @section Expressive marks
 
 @lilypondfile[quote]{expressive-headword.ly}
 
+This section lists various expressive marks that can be
+created in a score.
+
 @menu
 * Attached to notes::           
 * Curves::                      
@@ -21,17 +26,44 @@
 @node Attached to notes
 @subsection Attached to notes
 
+This section explains how to create expressive marks that are
+attached to notes: articulations, ornamentations, and dynamics.
+Methods to create new dynamic markings are also discussed.
+
 @menu
 * Articulations and ornamentations::  
 * Dynamics::                    
+* New dynamic marks::           
 @end menu
 
 @node Articulations and ornamentations
-@subsubsection Articulations and ornamentations
+@unnumberedsubsubsec Articulations and ornamentations
 
 @cindex articulations
 @cindex scripts
 @cindex ornaments
+@cindex espressivo
+@cindex fermata
+@cindex upbow
+@cindex downbow
+@cindex foot marks
+@cindex organ pedal marks
+@cindex turn
+@cindex open
+@cindex stopped
+@cindex flageolet
+@cindex reverseturn
+@cindex trill
+@cindex prall
+@cindex mordent
+@cindex prallprall
+@cindex prallmordent
+@cindex prall, up
+@cindex prall, down
+@cindex thumb marking
+@cindex segno
+@cindex coda
+@cindex varcoda
 
 A variety of symbols that denote articulations, ornamentations,
 and other performance indications can be attached to a note using
@@ -44,7 +76,7 @@ this syntax:
 The possible values for @var{name} are listed in @ref{List of
 articulations}.  For example:
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
 c4\staccato c\mordent b2\turn
 c1\fermata
 @end lilypond
@@ -66,88 +98,47 @@ signifying the articulation.  Predefined shorthands exist for
 and @notation{portato}.  Their corresponding output appears as
 follows:
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
 c4-^  c-+  c--  c-|
-c->   c-.  c-_
+c4->  c-.  c-_
 @end lilypond
 
 The rules for the default placement of articulations are defined
 in @file{scm/@/script@/.scm}.  Articulations and ornamentations
 may be manually placed above or below the staff, see
-@ref{Controlling direction and placement}.
-
-@cindex espressivo
-@cindex fermata
-@cindex upbow
-@cindex downbow
-@cindex foot marks
-@cindex organ pedal marks
-@cindex turn
-@cindex open
-@cindex stopped
-@cindex flageolet
-@cindex reverseturn
-@cindex trill
-@cindex prall
-@cindex mordent
-@cindex prallprall
-@cindex prallmordent
-@cindex prall, up
-@cindex prall, down
-@cindex thumb marking
-@cindex segno
-@cindex coda
-@cindex varcoda
+@ref{Direction and placement}.
 
 
 @snippets
 
-@c Send these snippets to Valentin for the LSR.
-
-The shorthands are defined in @file{ly/@/script@/-init@/.ly},
-where the variables @code{dashHat}, @code{dashPlus},
-@code{dashDash}, @code{dashBar}, @code{dashLarger},
-@code{dashDot}, and @code{dashUnderscore} are assigned default
-values.  The default values for the shorthands can be modified.
-For example, to associate the @code{-+} (@code{dashPlus})
-shorthand with the @notation{trill} symbol instead of the default
-@notation{+} symbol, assign the value @code{trill} to the variable
-@code{dashPlus}:
-
-@lilypond[verbatim,quote,ragged-right]
-\relative c'' { c-+ }
-dashPlus = "trill"
-\relative c'' { c-+ }
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{modifying-default-values-for-articulation-shorthand-notation.ly}
 
-The vertical ordering of scripts is controlled with the
-@code{script-priority} property.  The lower this number, the
-closer it will be put to the note.  In this example, the
-@code{TextScript} (the sharp symbol) first has the lowest
-priority, so it is put lowest in the first example.  In the
-second, the @notation{prall trill} (the @code{Script}) has the
-lowest, so it is on the inside.  When two objects have the same
-priority, the order in which they are entered decides which one
-comes first.
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=3]
-\once \override TextScript #'script-priority = #-100
-a4^\prall^\markup { \sharp }
-
-\once \override Script #'script-priority = #-100
-a4^\prall^\markup { \sharp }
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{controlling-the-vertical-ordering-of-scripts.ly}
 
 
 @seealso
 
-Music Glossary: @rglos{tenuto}, @rglos{accent}, @rglos{staccato},
+Music Glossary:
+@rglos{tenuto},
+@rglos{accent},
+@rglos{staccato},
 @rglos{portato}.
 
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Notation Reference:
+@ref{Direction and placement},
+@ref{List of articulations}.
+
+Installed Files:
+@file{scm/@/script@/.scm}.
+
+Snippets:
+@rlsr{Expressive marks}.
 
-Internals Reference: @internalsref{Script},
-@internalsref{TextScript}.
+Internals Reference:
+@rinternals{Script},
+@rinternals{TextScript}.
 
 
 @knownissues
@@ -157,9 +148,12 @@ MIDI rendering of the music.
 
 
 @node Dynamics
-@subsubsection Dynamics
+@unnumberedsubsubsec Dynamics
 
+@cindex absolute dynamics
 @cindex dynamics
+@cindex dynamics, absolute
+@funindex \ppppp
 @funindex \pppp
 @funindex \ppp
 @funindex \pp
@@ -179,18 +173,18 @@ MIDI rendering of the music.
 @funindex \rfz
 
 Absolute dynamic marks are specified using a command after a note,
-like @code{c4\ff}.  The available dynamic marks are @code{\ppppp},
-@code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p}, @code{\mp},
-@code{\mf}, @code{\f}, @code{\ff}, @code{\fff}, @code{\ffff},
-@code{\fp}, @code{\sf}, @code{\sff}, @code{\sp}, @code{\spp},
-@code{\sfz}, and @code{\rfz}.  The dynamic marks may be manually
-placed above or below the staff, see @ref{Controlling direction
-and placement}.
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+such as @code{c4\ff}.  The available dynamic marks are
+@code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
+@code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
+@code{\ffff}, @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp},
+@code{\spp}, @code{\sfz}, and @code{\rfz}.  The dynamic marks may
+be manually placed above or below the staff, see 
+@ref{Direction and placement}.
+
+@lilypond[verbatim,quote,relative=2]
 c2\ppp c\mp
-c\rfz c^\mf
-c_\spp c_\staccato^\ff
+c2\rfz c^\mf
+c2_\spp c^\ff
 @end lilypond
 
 @cindex hairpin
@@ -201,109 +195,69 @@ c_\spp c_\staccato^\ff
 @funindex \decr
 
 A @notation{crescendo} mark is started with @code{\<} and
-terminated with @code{\!} or an absolute dynamic.  A
-@notation{decrescendo} is started with @code{\>} and is also
-terminated with @code{\!} or an absolute dynamic.  @code{\cr} and
-@code{\decr} may be used instead of @code{\<} and @code{\>}.  They
-can be engraved either using a graphical sign (a
-@notation{hairpin}), or with textual signs.
-
-Because these marks are bound to notes, you must use spacer notes
-if multiple marks are needed during one note.
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-c\< c\! d\> e\!
-<< f1 { s4 s4\< s4\! \> s4\! } >>
+terminated with @code{\!}, an absolute dynamic, or an additional
+crescendo or decrescendo mark.  A @notation{decrescendo} mark is
+started with @code{\>} and is also terminated with @code{\!}, an
+absolute dynamic, or another crescendo or decrescendo mark.
+@code{\cr} and @code{\decr} may be used instead of @code{\<} and
+@code{\>}.  @notation{Hairpins} are engraved by default using this
+notation.
+
+@lilypond[verbatim,quote,relative=2]
+c2\< c\!
+d2\< d\f
+e2\< e\>
+f2\> f\!
+e2\> e\mp
+d2\> d\>
+c1\!
 @end lilypond
 
-This may give rise to very short hairpins.  To lengthen them, the
-following code can be used, for example:
-
-@example
-\override Voice.Hairpin #'minimum-length = #5
-@end example
+Spacer rests are needed to engrave multiple marks on one note.
 
-@noindent
-A @notation{hairpin} normally starts at the left edge of the
-beginning note and ends on the right edge of the ending note.  If
-the ending note falls on the downbeat, the @notation{hairpin} ends
-on the immediately preceding bar line.  The following example
-illustrates this behavior:
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-e4\< e2. e1\!
-\set hairpinToBarline = ##f
-e4\< e2. e1\!
+@lilypond[verbatim,quote,relative=2]
+c4\< c\! d\> e\!
+<< f1 { s4 s4\< s4\> s4\! } >>
 @end lilypond
 
-@cindex espressivo, articulation
+@cindex espressivo articulation
 
 In some situations the @code{\espressivo} articulation mark may be
-suitable to indicate a crescendo and decrescendo on the one note:
+the appropriate choice to indicate a crescendo and decrescendo on
+one note:
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-c2 b4 a g1\espressivo
-@end lilypond
-
-@cindex al niente
-@cindex niente, al
-
-Hairpins may be printed with a circled tip (al niente notation):
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-\override Hairpin #'circled-tip = ##t
-c2\< c\!
-c4\> c\< c2\!
+@lilypond[verbatim,quote,relative=2]
+c2 b4 a
+g1\espressivo
 @end lilypond
 
 @cindex crescendo
 @cindex decrescendo
 @cindex diminuendo
-@funindex \setTextCresc
-@funindex \setTextDim
-@funindex \setTextDecresc
-@funindex \setHairpinCresc
-@funindex \setHairpinDim
-@funindex \setHairpinDecresc
-
-You can use text saying @notation{cresc.}, @notation{decr.}, or
-@notation{dim.} instead of hairpins with the commands
-@code{\setTextCresc}, @code{\setTextDim}, and
-@code{\setTextDecresc}.  The corresponding
-@code{\setHairpinCresc}, @code{\setHairpinDim}, and
-@code{\setHairpinDecresc} will revert to hairpins again:
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-\setTextCresc
-c\< d e f\!
-\setHairpinCresc
-e\> d c b\!
-\setTextDecresc
-e\> d e f\!
-\setTextDecr
-c\> d e f\!
-\setTextDim
-e\> d c b\!
-@end lilypond
 
-You can also supply your own texts and change the style of the
-spanner line with the properties @code{\crescendoText},
-@code{\crescendoSpanner}, @code{\decrescendoText}, and
-@code{\decrescendoSpanner}.  Available values for the spanner
-properties are @code{hairpin}, @code{line}, @code{dashed-line},
-and @code{dotted-line}.  If unset, a hairpin crescendo is used:
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\set crescendoText = \markup { \italic "cresc. poco" }
-\set crescendoSpanner = #'dotted-line
-a'2\< a a a a a a a\!\mf
+Crescendos and decrescendos can be engraved as textual markings
+instead of hairpins.  The built-in commands that enable these text
+modes are @code{\crescTextCresc}, @code{\dimTextDecresc},
+@code{\dimTextDecr}, and @code{\dimTextDim}.  The corresponding
+@code{\crescHairpin} and @code{\dimHairpin} commands will revert to
+hairpins again:
+
+@lilypond[verbatim,quote,relative=2]
+c4\< d e f\!
+e4\> d c b\!
+\crescTextCresc
+c4\< d e f\!
+\dimTextDecresc
+e4\> d c b\!
+\crescHairpin
+c4\< d e f\!
 @end lilypond
 
-To create new dynamic marks or text that should be aligned with
-dynamics, see @ref{New dynamic marks}.
+To create new absolute dynamic marks or text that should be
+aligned with dynamics, see @ref{New dynamic marks}.
 
 Vertical positioning of dynamics is handled by
-@internalsref{DynamicLineSpanner}.
+@rinternals{DynamicLineSpanner}.
 
 
 @predefined
@@ -313,60 +267,157 @@ Vertical positioning of dynamics is handled by
 @funindex \dynamicDown
 @code{\dynamicDown},
 @funindex \dynamicNeutral
-@code{\dynamicNeutral}.
+@code{\dynamicNeutral},
+@funindex \crescTextCresc
+@code{\crescTextCresc},
+@funindex \dimTextDim
+@code{\dimTextDim},
+@funindex \dimTextDecr
+@code{\dimTextDecr},
+@funindex \dimTextDecresc
+@code{\dimTextDecresc},
+@funindex \crescHairpin
+@code{\crescHairpin},
+@funindex \dimHairpin
+@code{\dimHairpin}.
 
 
 @snippets
 
-Dynamics that occur at, begin on, or end on the same note will be
-vertically aligned.  If you want to ensure that dynamics are
-aligned when they do not occur on the same note, you can increase
-the @code{staff-padding} property.
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{setting-hairpin-behavior-at-bar-lines.ly}
 
-@example
-\override DynamicLineSpanner #'staff-padding = #4
-@end example
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{setting-the-minimum-length-of-hairpins.ly}
 
-@noindent
-You may also use this property if the dynamics are colliding with
-other notation.
+@cindex al niente
+@cindex niente, al
 
-@notation{Crescendi} and @notation{decrescendi} that cross a line
-break will be continued on the second line.  If they end on the
-first note of a new line, nothing will be printed on that line.
-To change this behavior, use
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{printing-hairpins-using-al-niente-notation.ly}
 
-@example
-\override Score.Hairpin #'after-line-breaking = ##t
-@end example
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{vertically-aligning-dynamics-across-multiple-notes.ly}
 
-Text style dynamic changes (such as @notation{cresc.} and
-@notation{dim.}) are printed with a dashed line showing their
-extent.  To suppress printing this line, use
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{hiding-the-extender-line-for-text-dynamics.ly}
 
-@example
-\override DynamicTextSpanner #'dash-period = #-1.0
-@end example
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{changing-text-and-spanner-styles-for-text-dynamics.ly}
 
 
 @seealso
 
 @c TODO: Add hairpin to glossary.
 
-Music Glossary: @rglos{crescendo}, @rglos{decrescendo}.
+Music Glossary:
+@rglos{crescendo},
+@rglos{decrescendo}.
 
-Learning Manual: @rlearning{Articulation and dynamics}.
+Learning Manual:
+@rlearning{Articulation and dynamics}.
 
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Notation Reference:
+@ref{Direction and placement},
+@ref{New dynamic marks}.
 
-Internals Reference: @internalsref{DynamicText},
-@internalsref{Hairpin}.  Vertical positioning of these symbols is
-handled by @internalsref{DynamicLineSpanner}.
+Snippets:
+@rlsr{Expressive marks}.
+
+Internals Reference:
+@rinternals{DynamicText},
+@rinternals{Hairpin},
+@rinternals{DynamicLineSpanner}.
+
+
+@node New dynamic marks
+@unnumberedsubsubsec New dynamic marks
+
+@cindex new dynamic marks
+@cindex dynamic marks, new
+
+The easiest way to create dynamic indications is to use
+@code{\markup} objects.
+
+@lilypond[verbatim,quote]
+moltoF = \markup { molto \dynamic f }
+
+\relative c' {
+  <d e>16 <d e>
+  <d e>2.._\moltoF
+}
+@end lilypond
+
+@cindex dynamics, editorial
+@cindex dynamics, parenthesis
+
+In markup mode, editorial dynamics (within parentheses or square
+brackets) can be created.  The syntax for markup mode is described
+in @ref{Formatting text}.
+
+@lilypond[verbatim,quote]
+roundf = \markup { \center-align { \line { \bold { \italic ( }
+         \dynamic f \bold { \italic ) } } } }
+boxf = \markup { \bracket { \dynamic f } }
+\relative c' {
+  c1_\roundf
+  c1_\boxf
+}
+@end lilypond
+
+By default, markup objects are aligned to the left side of a note
+head, but authentic dynamic marks are always centered on the note
+head.  New, centered dynamic marks can be created using the
+following function:
+
+@cindex make-dynamic-script
+
+@lilypond[verbatim,quote]
+sfzp = #(make-dynamic-script "sfzp")
+\relative c' {
+  c4 c c\sfzp c
+}
+@end lilypond
+
+@noindent
+The dynamic font only contains the characters @code{f,m,p,r,s} and
+@code{z}.  In order to use other font families, it is necessary to
+use markup mode in its Scheme form, as explained in
+@ref{Markup construction in Scheme}.
+
+@lilypond[verbatim,quote]
+moltoF = #(make-dynamic-script (markup 
+                      #:normal-text "molto"
+                      #:dynamic "f"))
+\relative c' {
+  <d e>16 <d e>
+  <d e>2..\moltoF
+}
+@end lilypond
+
+@noindent
+Font settings in markup mode are described in
+@ref{Common markup commands}.
+
+
+@seealso
+
+Notation Reference:
+@ref{Formatting text},
+@ref{Common markup commands},
+@ref{Markup construction in Scheme}.
+
+Snippets:
+@rlsr{Expressive marks}.
 
 
 @node Curves
 @subsection Curves
 
+This section explains how to create various expressive marks that
+are curved: normal slurs, phrasing slurs, breath marks, falls, and
+doits.
+
 @menu
 * Slurs::                       
 * Phrasing slurs::              
@@ -375,30 +426,44 @@ handled by @internalsref{DynamicLineSpanner}.
 @end menu
 
 @node Slurs
-@subsubsection Slurs
+@unnumberedsubsubsec Slurs
 
 @cindex slurs
 
-A @notation{slur} indicates that notes are to be played bound or
-@emph{legato}.  They are entered using parentheses:
+@notation{Slurs} are entered using parentheses:
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-f( g a) a8 b( a4 g2 f4)
+@lilypond[verbatim,quote,relative=2]
+f4( g a) a8 b(
+a4 g2 f4)
 <c e>2( <b d>2)
 @end lilypond
 
-Just as with ties, the direction of a slur can be specified with
-@code{\slur@emph{DIR}}, where @code{@emph{DIR}} is either
-@code{Up}, @code{Down}, or @code{Neutral} (@code{Neutral} is the
-default).  Slurs may be manually placed above or below the staff,
-see @ref{Controlling direction and placement}.
+Slurs may be manually placed above or below the notes, see
+@ref{Direction and placement}.
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-c4_( c) c^( c)
+@lilypond[verbatim,quote,relative=2]
+c2( d)
+\slurDown
+c2( d)
+\slurNeutral
+c2( d)
 @end lilypond
 
-Using this method, only one slur can be printed at once.  To print
-a long slur over a few small slurs, see @ref{Phrasing slurs}.
+Phrasing slurs must be used to print more than one slur at once.
+For details, see @ref{Phrasing slurs}.
+
+Slurs can be solid, dotted, or dashed.  Solid is the default slur
+style:
+
+@lilypond[verbatim,quote,relative=1]
+c4( e g2)
+\slurDashed
+g4( e c2)
+\slurDotted
+c4( e g2)
+\slurSolid
+g4( e c2)
+@end lilypond
 
 
 @predefined
@@ -419,49 +484,56 @@ a long slur over a few small slurs, see @ref{Phrasing slurs}.
 
 @snippets
 
-Some composers write two slurs when they want legato chords.  This
-can be achieved in LilyPond by setting @code{doubleSlurs},
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\set doubleSlurs = ##t
-<c e>4 ( <d f> <c e> <d f> )
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{using-double-slurs-for-legato-chords.ly}
 
 
 @seealso
 
-Music Glossary: @rglos{slur}
+Music Glossary:
+@rglos{slur}.
+
+Notation Reference:
+@ref{Direction and placement},
+@ref{Phrasing slurs}.
 
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Snippets:
+@rlsr{Expressive marks}.
 
-Internals Reference: @internalsref{Slur}.
+Internals Reference:
+@rinternals{Slur}.
 
 
 @node Phrasing slurs
-@subsubsection Phrasing slurs
+@unnumberedsubsubsec Phrasing slurs
 
 @cindex phrasing slurs
 @cindex phrasing marks
 @funindex \(
 @funindex \)
 
-A phrasing slur (or phrasing mark) connects notes and is used to
-indicate a musical sentence.  It is written using @code{\(} and
+@notation{Phrasing slurs} (or phrasing marks) that indicate a
+musical sentence are written using the commands @code{\(} and
 @code{\)} respectively:
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\time 6/4 c'\( d( e) f( e) d\)
+@lilypond[verbatim,quote,relative=2]
+c4\( d( e) f(
+e2) d\)
 @end lilypond
 
-Typographically, the phrasing slur behaves almost exactly like a
-normal slur.  However, they are treated as different objects.  A
-@code{\slurUp} will have no effect on a phrasing slur; instead,
-use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
-@code{\phrasingSlurNeutral}.  Phrasing slurs may be manually
-placed above or below the staff, see @ref{Controlling direction
-and placement}.
+Typographically, a phrasing slur behaves almost exactly like a
+normal slur.  However, they are treated as different objects; a
+@code{\slurUp} will have no effect on a phrasing slur.  Phrasing
+slurs may be manually placed above or below the notes, see
+@ref{Direction and placement}.
 
-You cannot have simultaneous phrasing slurs.
+@lilypond[verbatim,quote,relative=1]
+c4\( g' c,( b) | c1\)
+\phrasingSlurUp
+c4\( g' c,( b) | c1\)
+@end lilypond
+
+Simultaneous phrasing slurs are not permitted.
 
 
 @predefined
@@ -476,93 +548,104 @@ You cannot have simultaneous phrasing slurs.
 
 @seealso
 
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Notation Reference:
+@ref{Direction and placement}.
+
+Snippets:
+@rlsr{Expressive marks}.
 
-Internals Reference: @internalsref{PhrasingSlur}
+Internals Reference:
+@rinternals{PhrasingSlur}.
 
 
 @node Breath marks
-@subsubsection Breath marks
+@unnumberedsubsubsec Breath marks
 
 @cindex breath marks
 @funindex \breathe
 
 Breath marks are entered using @code{\breathe}:
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-c'4 \breathe d4
+@lilypond[verbatim,quote,relative=2]
+c2. \breathe d4
 @end lilypond
 
+Musical indicators for breath marks in ancient notation,
+divisiones, are supported.  For details, see @ref{Divisiones}.
+
 
 @snippets
 
-The glyph of the breath mark can be tuned by overriding the
-@code{text} property of the @code{BreathingSign} layout object
-with any markup text.  For example,
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{changing-the-breath-mark-symbol.ly}
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-c'4
-\override BreathingSign #'text
-  = #(make-musicglyph-markup "scripts.rvarcomma")
-\breathe
-d4
-@end lilypond
+@cindex caesura
+@cindex railroad tracks
+
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{inserting-a-caesura.ly}
 
 
 @seealso
 
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Notation Reference:
+@ref{Divisiones}.
+
+Snippets:
+@rlsr{Expressive marks}.
 @c @lsr{expressive,breathing-sign.ly}.
 
-Internals Reference: @internalsref{BreathingSign}
+Internals Reference:
+@rinternals{BreathingSign}.
 
 
 @node Falls and doits
-@subsubsection Falls and doits
+@unnumberedsubsubsec Falls and doits
 
 @cindex falls
 @cindex doits
 @funindex \bendAfter
 
 @notation{Falls} and @notation{doits} can be added to notes using
-the @code{\bendAfter} command:
+the @code{\bendAfter} command.  The direction of the fall or doit
+is indicated with a plus or minus (up or down).  The number
+indicates the pitch interval that the fall or doit will extend
+@emph{beyond} the main note.
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
 c2-\bendAfter #+4
-c-\bendAfter #-4
-c-\bendAfter #+8
-c-\bendAfter #-8
+c2-\bendAfter #-4
+c2-\bendAfter #+8
+c2-\bendAfter #-8
 @end lilypond
 
-The dash (@tie{-}) following the note name is @emph{required} when
-writing @notation{falls} and @notation{doits}.
+The dash (@tie{-}) immediately preceding the @code{\bendAfter}
+command is @emph{required} when writing falls and doits.
 
 
 @snippets
 
-The @code{shortest-duration-space} property may have to be tweaked
-to adjust the shape of @notation{falls} and @notation{doits}.
-
-@c Fix this snippet. The tweak does not work. -pm
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-\override Score.SpacingSpanner #'shortest-duration-space = #3.0
-c4-\bendAfter #+5
-c4-\bendAfter #-3
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{adjusting-the-shape-of-falls-and-doits.ly}
 
 
 @seealso
 
 @c TODO: add falls and doits to glossary.
-@c Music Glossary: @rglos{falls}, @rglos{doits}.
+@c Music Glossary:
+@c @rglos{falls},
+@c @rglos{doits}.
 
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Snippets:
+@rlsr{Expressive marks}.
 
 
 @node Lines
 @subsection Lines
 
+This section explains how to create various expressive marks that
+follow a linear path: glissandos, arpeggios, and trills.
+
 @menu
 * Glissando::                   
 * Arpeggio::                    
@@ -570,46 +653,45 @@ Snippets: @lsrdir{Expressive,Expressive-marks}
 @end menu
 
 @node Glissando
-@subsubsection Glissando
+@unnumberedsubsubsec Glissando
 
 @cindex glissando
 @funindex \glissando
 
-A @notation{glissando} is a smooth change in pitch.  It is denoted
-by a line or a wavy line between two notes.  A
-@notation{glissando} is created by attaching @code{\glissando} to
-a note:
+A @notation{glissando} is created by attaching @code{\glissando}
+to a note:
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-c2\glissando c'
-\override Glissando #'style = #'zigzag
+@lilypond[verbatim,quote,relative=2]
+g2\glissando g'
 c2\glissando c,
 @end lilypond
 
+Different styles of glissandi can be created.  For details, see
+@ref{Line styles}.
 
 @snippets
 
-@lilypond[verbatim,quote,ragged-right]
-I = \once \override NoteColumn #'ignore-collision = ##t
-
-\relative c' <<
-  { \oneVoice \stemDown f2 \glissando \stemNeutral a } \\
-  { \oneVoice \I c2 \glissando \I d, }
->>
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{contemporary-glissando.ly}
 
 
 @seealso
 
-Music Glossary: @rglos{glissando}
+Music Glossary:
+@rglos{glissando}.
+
+Notation Reference:
+@ref{Line styles}.
 
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Snippets:
+@rlsr{Expressive marks}.
 
 @c FIXME: I need to figure out what's up with these.  -gp
 @c @lsr{expressive,glissando.ly},
 @c @lsr{expressive,line-styles.ly}
 
-Internals Reference: @internalsref{Glissando}
+Internals Reference:
+@rinternals{Glissando}.
 
 
 @knownissues
@@ -619,131 +701,102 @@ supported.
 
 
 @node Arpeggio
-@subsubsection Arpeggio
+@unnumberedsubsubsec Arpeggio
 
 @cindex arpeggio
 @cindex broken chord
+@cindex chord, broken
 
-You can specify an @notation{arpeggio} (also known as a
-@notation{broken chord}) on a chord by attaching an
-@code{\arpeggio} to the chord:
+An @notation{arpeggio} on a chord (also known as a broken chord)
+is denoted by appending @code{\arpeggio} to the chord construct:
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-<c e g c>\arpeggio
+@lilypond[verbatim,quote,relative=1]
+<c e g c>1\arpeggio
 @end lilypond
 
-A square bracket on the left, denoted by @code{\arpeggioBracket},
-is used to indicate that the chord should @emph{not} be
-arpeggiated:
+The direction of an arpeggio is indicated by adding an arrowhead
+to the wiggly line.  The commands @code{\arpeggioArrowUp} and
+@code{\arpeggioArrowDown} are used for this task.
+@code{\arpeggioNormal} reverts back to an arrow-less arpeggio:
+
+@lilypond[verbatim,quote,relative=1]
+\arpeggioArrowUp
+<c e g c>2\arpeggio
+\arpeggioArrowDown
+<c e g c>2\arpeggio
+\arpeggioNormal
+<c e g c>1\arpeggio
+@end lilypond
+
+The command @code{\arpeggioBracket} can be used to create a square
+bracket on the left of a chord, indicating that the chord should
+@emph{not} be arpeggiated.  @code{\arpeggioNormal} reverts back
+to a regular arpeggio:
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
+@lilypond[verbatim,quote,relative=1]
+<c e g c>2
 \arpeggioBracket
-<c e g c>\arpeggio
+<c e g c>2\arpeggio
+\arpeggioNormal
+<c e g c>1\arpeggio
 @end lilypond
 
-The direction of the arpeggio can be denoted by adding an
-arrowhead to the wiggly line.  This is done with the commands
-@code{arpeggioUp} and @code{arpeggioDown}.  @code{arpeggioNeutral}
-reverts to the arrow-less version:
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\new Voice {
-  \arpeggioUp
-  <c e g c>\arpeggio
-  \arpeggioDown
-  <c e g c>\arpeggio
-  \arpeggioNeutral
-  <c e g c>\arpeggio
-}
+A @emph{parenthesis} style bracket may be attached to a chord
+construct instead of a square bracket.
+
+@lilypond[verbatim,quote,relative=1]
+<c e g c>2
+\arpeggioParenthesis
+<c e g c>2\arpeggio
+\arpeggioNormal
+<c e g c>1\arpeggio
 @end lilypond
 
+Arpeggios can be explicitly written out with ties.  For more
+information, see @ref{Ties}.
 
 @predefined
 
 @funindex \arpeggio
 @code{\arpeggio},
-@funindex \arpeggioUp
-@code{\arpeggioUp},
-@funindex \arpeggioDown
-@code{\arpeggioDown},
-@funindex \arpeggioNeutral
-@code{\arpeggioNeutral},
+@funindex \arpeggioArrowUp
+@code{\arpeggioArrowUp},
+@funindex \arpeggioArrowDown
+@code{\arpeggioArrowDown},
+@funindex \arpeggioNormal
+@code{\arpeggioNormal},
 @funindex \arpeggioBracket
-@code{\arpeggioBracket}.
+@code{\arpeggioBracket},
+@funindex \arpeggioParenthesis
+@code{\arpeggioParenthesis}.
 
 
 @snippets
 
-In a @code{PianoStaff}, it is possible to let an arpeggio cross
-between the staves by setting the property
-@code{PianoStaff}.@code{connectArpeggios}.
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{creating-cross-staff-arpeggios-in-a-piano-staff.ly}
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\new PianoStaff <<
-  \set PianoStaff.connectArpeggios = ##t
-  \new Staff { <c' e g c>\arpeggio }
-  \new Staff { \clef bass <c,, e g>\arpeggio }
->>
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{creating-cross-staff-arpeggios-in-other-contexts.ly}
 
-The same can be accomplished in contexts other than
-@code{PianoStaff} if the @code{Span_arpeggio_engraver} is included
-in the Score context.
-
-@lilypond[verbatim,quote,ragged-right]
-\score {
-  \new StaffGroup {
-    \set Score.connectArpeggios = ##t
-    <<
-      \new Voice \relative c' {
-        <e g>4\arpeggio
-      }
-      \new Voice  \relative c {
-        \clef bass
-        <c e>4\arpeggio
-      }
-    >>
-  }
-  \layout {
-    \context {
-      \Score
-      \consists "Span_arpeggio_engraver"
-    }
-  }
-}
-@end lilypond
-
-Similarly, an arpeggio can be drawn across notes in different
-voices on the same staff if the @code{Span_arpeggio_engraver} is
-moved to the Staff context:
-
-@lilypond[verbatim,quote,ragged-right]
-\new Staff
-\with {
-  \consists "Span_arpeggio_engraver"
-} \relative c' {
-  \set Staff.connectArpeggios = ##t
-    <<
-    {<e' g>4\arpeggio <d f> <d f>2 }
-  \\
-  {<d, f>2\arpeggio  <g b>2  }
-  >>
-}
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{creating-arpeggios-across-notes-in-different-voices.ly}
 
 
 @seealso
 
-@c TODO: Add 'broken chord' to glossary.
-
-Music Glossary: @rglos{arpeggio}
+Music Glossary:
+@rglos{arpeggio}.
 
-Notation Reference: @ref{Ties}, for writing out arpeggios.
+Notation Reference:
+@ref{Ties}.
 
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Snippets:
+@rlsr{Expressive marks}.
 
-Internals Reference: @internalsref{Arpeggio},
-@internalsref{PianoStaff}.
+Internals Reference:
+@rinternals{Arpeggio},
+@rinternals{PianoStaff}.
 
 
 @knownissues
@@ -752,61 +805,87 @@ It is not possible to mix connected arpeggios and unconnected
 arpeggios in one @code{PianoStaff} at the same point in
 time.
 
+The parenthesis-style arpeggio brackets do not work for
+cross-staff arpeggios.
+
 
 @node Trills
-@subsubsection Trills
+@unnumberedsubsubsec Trills
 
 @cindex trills
 @funindex \trill
 
-Short @notation{trills} are printed with @code{\trill} like normal
-articulation; see @ref{Articulations and ornamentations}.
+Short @notation{trills} without an extender line are printed with
+@code{\trill}; see @ref{Articulations and ornamentations}.
 
-Long running @notation{trills} are made with
+Longer trills with an extender line are made with
 @code{\startTrillSpan} and @code{\stopTrillSpan}.  In the
-following example, a long running @notation{trill} is shown
-combined with grace notes.  To achieve precise control of the
-placement of the grace notes, see @ref{Grace notes}.
+following example, the trill is combined with grace notes.  To
+achieve precise control over the placement of the grace notes, see
+@ref{Grace notes}.
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
 c1 \afterGrace
 d1\startTrillSpan { c16[\stopTrillSpan d] }
 c4
 @end lilypond
 
 @cindex pitched trills
+@cindex trills, pitched
 
-@notation{Trills} that should be executed on an explicitly
-specified pitch can be typeset with the command
-@code{\pitchedTrill} using the following syntax:
+Trills that require an auxiliary note with an explicit pitch can
+be typeset with the @code{\pitchedTrill} command.  The first
+argument is the main note, and the second is the @emph{trilled}
+note, printed as a stemless note head in parentheses.
 
-@example
-@code{\pitchedTrill} @var{mainnote} @code{\startTrillSpan}
-@var{trillnote} @var{endnote} @code{\stopTrillSpan}
-@end example
+@c This syntax example doesn't look nice. -pm
+
+@c @example
+@c @code{\pitchedTrill} @var{mainnote} @code{\startTrillSpan}
+@c @var{trillnote} @var{endnote} @code{\stopTrillSpan}
+@c @end example
 
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\pitchedTrill e2 \startTrillSpan fis
+@lilypond[verbatim,quote,relative=1]
+\pitchedTrill e2\startTrillSpan fis
 d\stopTrillSpan
 @end lilypond
 
-@noindent
-The first argument is the main note.  The pitch of the second is
-printed as a stemless note head in parentheses.
+In the following example, the second pitched trill is ambiguous;
+the accidental of the trilled note is not printed.  As a
+workaround, the accidentals of the trilled notes can be forced.
+The second measure illustrates this method:
+
+@lilypond[verbatim,quote,relative=2]
+\pitchedTrill eis4\startTrillSpan fis
+g\stopTrillSpan
+\pitchedTrill eis4\startTrillSpan fis
+g\stopTrillSpan
+\pitchedTrill eis4\startTrillSpan fis
+g\stopTrillSpan
+\pitchedTrill eis4\startTrillSpan fis!
+g\stopTrillSpan
+@end lilypond
 
 
 @predefined
 
-@code{\startTrillSpan},
 @funindex \startTrillSpan
-@code{\stopTrillSpan}.
+@code{\startTrillSpan},
 @funindex \stopTrillSpan
+@code{\stopTrillSpan}.
 
 
 @seealso
 
-Music Glossary: @rglos{trill}
+Music Glossary:
+@rglos{trill}.
+
+Notation Reference:
+@ref{Articulations and ornamentations},
+@ref{Grace notes}.
 
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Snippets:
+@rlsr{Expressive marks}.
 
-Internals Reference: @internalsref{TrillSpanner}
+Internals Reference:
+@rinternals{TrillSpanner}.