Comment #16 on issue 2070 by [email protected]: Patch: Don't wrap EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Again, concerning comment #14 and compatibility. I have tried looking in the engravers concerning how to make things behave as closely to currently as possible. The basic concern is how to make c-. equivalent to <c>-. instead of <c-.>.
The way to achieve that would be to let the EventChord engraver cater for those cases where "articulations" on a NoteEvent is to be treated differently from an articulation event merely occuring simultaneously with a NoteEvent. This would presumably be done by letting EventChord convert articulations on NoteEvents into stream events involving both note event and articulation, while NoteEvents in itself would not do anything special with its articulations but let the normal music engraver execute them in parallel with them.
I don't feel particularly comfortable with attempting this kind of surgery (I really don't have much of a clue about LilyPond's engraving backends), but it would more or less keep the existing equivalences of input and result intact.
_______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
