On Sunday, September 25, 2011, D. Michael McIntyre wrote: > I'll see what I can do with it, starting by having a look at the patch.
It looks good! With so many new files added, we really need to get someone who isn't you or me to try building and make sure I added all the files. I _think_ I did, but it's so easy to screw that up. So what is music XML good for, in order to test it? It seems like exporting from Rosegarden and importing into MusE Score is a good place to start? I tried that with an anacrusis test file I had close at hand, and spotted some good things and some bad things straight off. Good: After importing the .xml file into mscore, the bar lines came out correctly! LilyPond export doesn't even do that yet, and we're relying on LilyPond to provide print functionality, which is kind of pitiful. Bad: There were no repeat signs, and all the redundant clefs at the start of each segment (needed for Rosegarden's internal use, and can't be eliminated, but are normally hidden) were exported and displayed. I can't remember if I offered you commit access already. Coming up with a big new piece of work like this means I'd really prefer to grant you access to commit your own fixes from here out, instead of managing a series of patches coming from your direction when you need to tweak this work. Just establish a SourceForge ID and I'll take care of it directly. -- D. Michael McIntyre ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
