Another interesting option might be the new library from Frescobaldi. Peter is
using it for the export side of things, and it might be useful for import too.
IIUC Frescobaldi can write a .ly file from its internal DOM representation. I
think there is much in common between translating that DOM _to_ XML and to do
the contrary. _Im_porting has the additional benefit of providing a 1to1
representation that can be directly converted to a LilyPond file which isn't so
easy the other way round.
Urs
Johan Vromans <jvrom...@squirrel.nl> schrieb am 20.03.2014:
>Francisco Vila <paconet....@gmail.com> writes:
>
>> This is true but he is talking about using "their MusicXML importer"
>I
>> think.
>>
>> Without knowing all the internal details, I can say this sounds easy
>> but it is Not. Because, it imports, and converts to what exactly?
>> Certainly not to a LilyPond-usable representation of the music.
>
>All I wanted to say is that there exists a piece of open source
>software
>that does a decent job of converting MusicXML into LilyPond. It may be
>worth considering to clone this tool, strip everything but the MusicXML
>importer and LilyPond exporter and proceed from there.
>
>Of course it is not trivial, but continuously enhancing the current
>MusicXML.py isn't trivial either.
>
>Alternatively, we could give the MuseScore LilyPond exporter some live
>it needs to keep it alive.
>
>-- Johan
>
>_______________________________________________
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Diese Nachricht wurde mit <a
href="https://play.google.com/store/apps/details?id=com.onegravity.k10.pro2";><b>K-@
Mail</b></a> gesendet.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
