Re: [Lilypond-auto] Issue 1698 in lilypond: Slurs and ties are not correct over repeats

[lilypond]

Comment #40 on issue 1698 by address@hidden: Slurs and ties are not correct  
over repeats
http://code.google.com/p/lilypond/issues/detail?id=1698

Regarding comment #38: please don't misrepresent me.  It is not even  
possible to implement what you claim I have proposed.  The actual proposal  
is sketched in <URL:https://codereview.appspot.com/7424049#msg17>.

If we make \broken a music function with a single postevent as argument,  
the proposed syntax would be
\broken( a b c) d
and, for an ending spanner, something like
a b( c d \broken)

That's the user interface.  It does not reflect on the representation as  
music function.

Ties in the input don't really have more than one spanner direction, so one  
needs to decide what \broken~ is supposed to mean.  Since we already have  
\repeatTie, it might imply an ending spanner.  Not sure about the best  
course for ties, but for symmetric spanners, \broken is a rather  
straightforward user interface.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings