[EMAIL PROTECTED] writes:
> again to this email) is fairly common in the literature where a figure
> starts in one hand and ends in the other. And LilyPond can already typeset
> across staves, it's just that you have to resort to an unbelievable amount
> of trickery to get things to look right (as you can see in the example).
> It's an awful lot of work (and not very readable) just to get phrase marks
> in the music--there has to be a better way of doing this
I still don't understand what you really want. Let me explain my
reasoning
* A slur has to be in the same Voice context as the notes it spans.
You need that to keep a slur from colliding with all the notes it
spans.
* So, to make a slur cross staffs, you make the Voice it is in cross
staffs.
* You do this by inserting a `staff switch', which is written as
\translator Staff = nameOfOtherStaff
You can hide this complexity with identifiers.
switchUp = \translator Staff = upstaff
For this thing to work, you have to add one (1) extra \switchUp
statement. I don't understand how you can possibly have it any
simpler.
If I understand correctly, you want to have a some sort of special
marker (hypothetical syntax: \( and \) ), so you can put the up staff
notes in the up staff, and the down staff notes in the downstaff, and
add a \( to the downstaff starting note, and a \) to the up staff
ending note, that makes the slur magically cross staffs?
Aside from the implementation issues (they would be hairy), it gives
rise to ambiguities: for example, what if there are multiple slurs
crossing staffs upwards: how would you know if the slurs should cross
or not ?
picture:
upper ===========\)C=
staff =======E===\)D=
F
lower ===B\(=========
staff ===A\(=========
( A-F are note heads. \( \) mark slur endings/ beginnings.)
How can lily figure out if you have a slurs from A to C and B to D or
from A to D and B to C? If and how should collisions with E and F be
handled?
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
