diff options
| author | David Kastrup <dak@gnu.org> | 2016-08-15 19:09:52 +0200 |
|---|---|---|
| committer | David Kastrup <dak@gnu.org> | 2016-08-21 18:59:39 +0200 |
| commit | aa516b66c0e603146f94bee9dc74408262792977 (patch) | |
| tree | 585aade593aa2ba85bcdd93c067b4684cd4628ef | |
| parent | 6fcbd2a18b171f56ec873520a3c3de2e028a0a04 (diff) | |
Issue 4956/3: Augment warning about \retrograde
Ties work now, but the documentation points out a lot of other
shortcomings.
| -rw-r--r-- | Documentation/notation/pitches.itely | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/Documentation/notation/pitches.itely b/Documentation/notation/pitches.itely index 0699239db5..bfed32447e 100644 --- a/Documentation/notation/pitches.itely +++ b/Documentation/notation/pitches.itely @@ -903,9 +903,14 @@ music = \relative { c'8. ees16( fis8. a16 b8.) gis16 f8. d16 } @end lilypond @knownissues -Manual ties inside @code{\retrograde} will be broken and -generate warnings. Some ties can be generated automatically -by enabling @ref{Automatic note splitting}. +@code{\retrograde} is a rather simple tool. Since many events are +@q{mirrored} rather than exchanged, tweaks and directional +modifiers for opening spanners need to be added at the matching +closing spanners: @code{^(} needs to be ended by @code{^)}, every +@code{\<} or @code{\cresc} needs to be ended by @code{\!} or +@code{\endcr}, every @code{\>} or @code{\decr} needs to be ended +by @code{\enddecr}. Property-changing commands/overrides with a +lasting effect will likely cause surprises. @seealso Notation Reference: |