[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: issues with musicxml2ly

From: Knut Petersen
Subject: Re: issues with musicxml2ly
Date: Sun, 14 Jul 2019 22:59:41 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2

Hi Gilberto!
Try if replacing

    musicxml ...


    python2 $(grep -o '"[^$^"]*$me"' `which musicxml2ly` | sed -e 's/"//g' -e 
's/$me/musicxml2ly/')  ...
Yes, that does seem to fix the issue! The .ly file created by musicxml2ly does not have the encoding and strange character issues and compiles normally.

So edit your musicxml2ly wrapper script (the file given by 'which musicxml2ly'):

Delete lines 2, 3 and 4.
In the last line, replace

   exec "/.../python"



Bug 1:
Musicxml2ly is incompatible to the python2 distributed with the installers.
Musicxml2ly needs at least python2 2.7.0, lilypond installers provide python 

Bug 2:
During building of lilypond with GUB musicxml2ly is used intensively.
Alas, musicxml2ly does not fail because erroneously not GUB's own python 2.4.5
but the system's python2 is used.

As none of the people involved in developing, testing and building the
lilypond distributions is using a python2 < 2.7.0, nobody realized that
there is a problem for a number of years.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]