> On Apr 23, 2015, at 12:30 AM, Carl Sorensen <c_soren...@byu.edu> wrote: > > On 4/22/15 8:59 PM, "Paul Morris" <p...@paulwmorris.com> wrote: >> >> Ok, the problem was that your music file was for LilyPond 2.19 and >> jianpu3.ly only works with 2.18. > > Have you proposed adding this to LilyPond? It seems like this would be a > promising thing to add to the core, since it's another standard notation.
I haven’t but I’m not opposed to that eventually. As Werner notes there is still a lot to do. I haven’t done anything with refining the appearance. I’m just trying to get the ball rolling by getting all the “moving parts” in place (since I’m already familiar with the techniques for implementing alternative notation systems in LilyPond). Ideally someone who uses and really knows Jianpu well could take it over and refine it. (Maybe David Zhang? or Silas Brown who did the “jianpu-ly" Python approach? [1] Maybe some of the appearance work could be repurposed from the output of “jianpu-ly”? I haven’t tried it.) I don’t really have the time right now to refine it and see it all the way through to adding it to the core. [1] http://people.ds.cam.ac.uk/ssb22/mwrhome/jianpu-ly.html > I guess the biggest problem we have with adding it to the core is that it > uses Scheme engravers, rather than C++ engravers, and we have no mechanism > for documenting Scheme engravers. Yes, that’d be a problem. > I think it would be worthwhile posting this to liypond-devel to start a > discussion about adding it to the core. Thanks, although I’m not sure it’s worth starting that discussion just yet… -Paul _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
