-Eluze <[email protected]> writes: > compiling LSR 632 gives following warnings: > > warning: cannot find start of text spanner > warning: unterminated text spanner > > and the output is created without a barre. > > any ideas?
Fallout from <URL:http://code.google.com/p/lilypond/issues/detail?id=2240>. The code assumes that every rhythmic event is wrapped inside of an EventChord. Which is no longer the case. This snippet can be fixed only manually. One option would be to do this hard way, by rewriting the code thoroughly. Another option would be to provide a compatibility function \eventChordWrap aka (event-chord-wrap! ...) (suggestions for a better name?) that would rewrap the music in its argument in the manner that the analysis function expects. While this function would still need to get placed manually in strategic locations because convert-ly can't analyze the music thoroughly enough to figure out which functions are affected, this would require less thought to apply. It would not really be a good option for LSR code except as a stopgap measure since it adds one layer of confusion. This is Documentation/snippets/new/bar-chords-notation-for-guitar--with-text-spanner.ly in our source tree. I'll fix this one in the thorough way, but would like to hear opinions regarding the above suggestion for reasonably brainless conversion wrappers as outlined above. -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
