summaryrefslogtreecommitdiff
path: root/Documentation/notation/expressive.itely
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/notation/expressive.itely')
-rw-r--r--Documentation/notation/expressive.itely7
1 files changed, 5 insertions, 2 deletions
diff --git a/Documentation/notation/expressive.itely b/Documentation/notation/expressive.itely
index 60f0cc66c0..3c249389c2 100644
--- a/Documentation/notation/expressive.itely
+++ b/Documentation/notation/expressive.itely
@@ -304,7 +304,7 @@ or @notation{decrescendo} mark, it will end at the centre of the note
that has the next @code{\<} or @code{\>} assigned to it. The next
hairpin will then start at the right edge of the same note
instead of the usual left edge had it been terminated with @code{\!}
-before.
+before. A hairpin ending on a downbeat will stop at the preceding bar line.
@lilypond[verbatim,quote]
\relative {
@@ -446,6 +446,8 @@ items such as text scripts, text spanners, and piano pedal marks.
@snippets
+@cindex hairpins at bar lines
+
@lilypondfile[verbatim,quote,texidoc,doctitle]
{setting-hairpin-behavior-at-bar-lines.ly}
@@ -683,7 +685,8 @@ occurences of outer slurs actually indicate phrasing, and phrasing
slurs may overlap a regular slur, see @ref{Phrasing slurs}. When
multiple regular slurs are needed in a single @code{Voice},
matching slur starts and ends need to be labelled by preceding
-them with @code{\=} followed by an identifying number or string.
+them with @code{\=} followed by an identifying key (a symbol or
+non-negative integer).
@lilypond[verbatim,quote]
\fixed c' {