Valentin Villenave wrote:
> seeing your work getting forgotten is understandably frustrating, but
> I'm afraid this is but a consequence of our lack of resources (people,
> time, energy). I *could* mark the issue as "started" if you do provide
> us with a possible way to address the problem, not necessarily a patch
> but even pseudocode that someone can help you implement. That *might*
> give it more visibility -- but please keep in mind that there are
> currently 290 open issues in our tracker.
Hi Valentin,
I didn't mean to express any frustration with the process - I just
figured that it probably got lost amidst a lot of bug updates on
bug-lilypond. My goal at the moment with this bug is to decide whether
it's an issue with the code form my patch or an issue with the
melisma_busy() function. I'm happy to try to address the problem
further, but need some guidance as to where I should be looking - should
melisma_busy() know about the melisma being extended with underscores in
the lyrics, or should an additional check be added in the extender engraver?
Thanks,
Chris
--
Chris Snyder
Adoro Music Publishing
1-616-828-4436 x800
http://www.adoromusicpub.com
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel