On 2018-03-29 13:33, Kieren MacMillan wrote:
Hi Mats,
Just use the new features of version 2.19:
I tried that (see a previous post on this thread), but there are collisions (see a
separate "bug?" thread).
Did you not find that the slurs collide with the noteheads on your machine?
Right, now that you mention it. It seems to happen as soon as you
specify the slur per note head instead of for the full chord. Looking at
the examples in
http://lilypond.org/doc/v2.19/Documentation/changes/index.html, the
intention is probably to make it clear exactly which note head in the
chord the slur starts from, but in this particular example it seems to
fail for two reasons:
- The horizontal distance between the two notes is very short, and the
slur is not shortened sufficiently.
- For slurs attached to a bottom or top note of a chord, it would make
sense to add some vertical spacing, similar to the spacing used when the
slur is attached to the full chord, since there's no uncertainty about
which of the notes the slur starts from.
Regarding the latter issue, it would be worthwhile to check with Gould
if there is a typesetting convention to distinguish between a slur that
starts from the top note of a chord and a slur that starts from the full
chord, as Lilypond currently does it, or if these two situations should
be typeset the same.
Sorry about double posting already posted solutions, I follow the
mailing list in Digest mode, so there was some delay.
/Mats
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user