Re: musicxml2ly formatting

[pls]

Martin,

IINM Julien Lerouge and me are the only ones who currently work on musicxml2ly.   We publish our results on https://github.com/Philomelos/lilypond-musicxml2ly-dev.  Feel free to use it and help to improve it!  Some of our latest improvements:

• recognition of <credit>-Elements (title, composer, poet…)
• new command line options, such as --no-system-breaks; --no-page-breaks; --no-page-margins; --no-stem-directions
• automatic indentation of long instrument names
• automatic update of the LilyPond-Code with convert-ly (after the conversion)
• quite a few tiny xml examples

You are right, the resulting LilyPond files are not optimized.  To be honest: this is not at all on our priority list.  There are scores of more important bugs to kill.  But again we wouldn't mind some help!

Your plans to test a large collection of xml scores sounds very interesting!  We use musicxml2ly on http:/philomelos.net to render xml files (Public Domain and CC-licenses).  Feel free to contact me if you are interested in an invitation to the beta version of the platform.

hth

patrick

Am 20.03.2013 um 10:31 schrieb Martin Tarenskeen <address@hidden>:

Hi,

Musicxml2ly is a nice tool, even if the output is quite often not perfect and needs manual editing to - often easily - fix errors. (I have plans to test a large collection of xml scores, and make a list of all strange and/or bad results I'm encountering. But that's not what this message is about)

Fixing errors in complex lilypond files is easier when the file is nicely formatted. But IMO the output from music2xml, even if syntactically correct, often looks ugly. When I use frescobaldi's formatting tool things already look much better.

Is muscxml2ly's ugly output formatting a matter of  personal taste and style, or is this an issue worth to be added to the buglist?

--

MT

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user