On Wed, 09 Apr 2008 00:21:36 +0200 Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Quoting Graham Percival <[EMAIL PROTECTED]>: > > 2) it would of course be nice to automate this. At the moment, I > > can't see why this would take more than five hours. Maybe 15 > > hours if the person had never touched python before. > > See > http://lists.gnu.org/archive/html/bug-lilypond/2007-12/msg00156.html > I don't think the problem is that easy, especially since the music > expression may in the general case contain an arbitrarily deep > nesting of {} and <<>>, which means that you cannot use regular > expressions. I'm not really comfortable with regular expressions, so I wasn't going to suggest this anyway. :) As for nesting, we could simply count the number of { } and << >> to figure out when the expression is over. My solutions often end up quite hack-ish, but they work. As long as a human can explain to me what they want done, I can get the result... or in this case, I can teach somebody how to do it themselves. The first step would be simply to get a working program that does this, with no attempt being made to integrate it with convert-ly. Once we had working code, we'd investigate merging it or simply leaving it as a standalone tool for that particular conversion. Besides, these's nothing wrong -- and quite a few things right -- about inexperienced programmers rewriting code. :) Cheers, - Graham _______________________________________________ lilypond-user mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-user
