David, I saw that Colin had opened a tracker for your *ly file
http://code.google.com/p/lilypond/issues/detail?id=2445 I'm not a code developer, however I think it might be better to also open a Rietveld issue so that it gets a proper review, from my own experience, it is more likely to be looked at there than in the google tracker - simply because it is easier to read and comment inline. I don't know if you are familiar with that process, then if you are serious about getting this into the LilyPond code, you can work on it here and post the suggested changes etc. I fear otherwise it will stagnate *just* an attachment on a tracker. You can use git-cl to ease the process of uploading and updating both Rietveld and the tracker at the same time. http://lilypond.org/doc/v2.15/Documentation/contributor/summary-for-experienced-developers It doesn't mean that it has to compile necessarily or be perfect from the 'start' (for instance Mike Solomon often throws up 'concept' patches or 'work in progress' patches/code to Rietveld for comment. Sometimes they die there but more often than not they get improved very quickly simply because of the way to compare and share information in Rietveld. regards James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel