Thanks for the updates; I have places they will help!
On simultaneous slurs, I guess that the identifiers were introduced in
2.20, later than I've revisited that part of the manuals - the 2.18
learning manual still states the prohibition.
As an aside to that, I wonder if it would be worth while to restrict
access to older manuals by Google. A Google search (which I often use
to include other sources of information and hints) more often than not
presents an older version of LilyPond documentation, and I try to
remember to change the URL to 2.22 each time!
Paul
On 15/09/2021 12:00:35, "David Kastrup" <d...@gnu.org> wrote:
>Paul Hodges <p...@cassland.org> writes:
>
>> It's not causing your problem, but why use phrasing slurs: " \(" "\)?
>> Plain slurs: "(" ")" are that bit easier to write and read. They are,
>> as far as I know, identical in behaviour
>
>They aren't. They are typographically outward from normal slurs and are
>played differently, something which is quite relevant in the MIDI
>rendition.
>
>> - I think phrasing slurs were simply introduced to get over the
>> restriction that slurs cannot be nested in a voice.
>
>They can, by identifying the corresponding slurs, for example by
>preceding them with \=1 and \=2, respectively.
>
>--
>David Kastrup
