Hello! Thanks Kieren! I'll look in to the snippet link you sent. It'll probably require some understanding from my part. There's so many things with Lilypond that's so difficult. Especially for me without any experience at all in the type of workflow that Lilypond use.
Best wishes! P Peter Danemo Krukmakargatan 33 B 118 51 Stockholm Tel: +46-70-653 21 91 > 24 jan 2015 kl. 22:55 skrev Kieren MacMillan <kieren_macmil...@sympatico.ca>: > > Hi all, > >> Lastly got this help from Marc Hohl: >> http://lsr.di.unimi.it/LSR/Item?id=336 > > The linked issue (https://code.google.com/p/lilypond/issues/detail?id=1228) > currently has a status of “abandoned” — well, at least the associated patch > does, if not the whole issue. > > Is there a technical reason why the most up-to-date engraver (e.g., > https://github.com/openlilylib/openlilylib/blob/c53380f5ca460d244a017389dc4bcb79a3f04d14/editorial-tools/merge-rests-engraver/definition.ily) > has not been (or cannot be) rolled into the main Lilypond codebase? Or is it > technically sound, and now it's only a matter of somebody making an > appropriate/official patch and submitting it? > > The merged output is definitely standard engraving practice, so it would be > nice to see this enhancement in Lilypond, if the coding is already done (or > at least very close). > > Thanks, > Kieren. > _______________________ > > Kieren MacMillan, composer > www: <http://www.kierenmacmillan.info> > email: i...@kierenmacmillan.info _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user