Re: issues with musicxml2ly

[Paul Hodges]

Thanks very much for this!

I couldn't work out how your suggested changes can be applied in a 
Windows installation, so instead I did the following:
(1) Installed Python 2.7.14 in the system (but without adding it to the 
path);
(2) Used the following command (assuming default installation paths) in 
a standard command window to run it in the directory containing 
MyMusicFile.xml:

         C:\Python27\python.exe "C:\Program Files 
(x86)\Lilypond\usr\bin\musicxml2ly.py" --nd --nrp --npl --nsd 
--no-beaming --language=english MyMusicFile.xml"

This works perfectly for me, and is a significant improvement to 
Lilypond for my usage!

Regards,
Paul Hodges

On 14/07/2019 21:59:41, "Knut Petersen" <address@hidden> 
wrote:

>Hi Gilberto!
>>>Try if replacing
>>>
>>>     musicxml ...
>>>
>>>with
>>>
>>>     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"
>
>with
>
>    python2
>
>
>Bug 1:
>Musicxml2ly is incompatible to the python2 distributed with the installers.
>Musicxml2ly needs at least python2 2.7.0, lilypond installers provide python 
>2.4.5
>
>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.
>
>Knut
>
>
>_______________________________________________
>bug-lilypond mailing list
>address@hidden
>https://lists.gnu.org/mailman/listinfo/bug-lilypond