Le 26/08/2018 à 15:15, Victor Rouanet a écrit :
Same result for me. According to Phil Homes in the lilypond-user
topic, the shlex module (used by musicxml2ly in utilities.py) didn't
support unicode input prior to Python 2.7.3.
According to David Wright*
I mi
Le 26/08/2018 à 12:56, Federico Bruni a écrit :
Victor, please keep the list in Cc.
Sorry, newbie error :-)
I was using lilypond packaged by Fedora, which uses python2 installed
on the system (currently 2.7.15).
I've now installed 2.19.82 from lilypond.org, which uses the bundled
python .
Good morning,
I'm having an issue with musicxml2ly, installed with a manually
downloaded version on lilypond 2.19.82.
I exported a musicxml file from Musescore, then converted it to lilypond
source with musicxml2ly without error. However, when I try to compile it
with lilypond, I get the fol
Good evening everyone,
I hope I'm posting to the right place. I'm a music student and frequent
lilypond user, especially for orchestral scores, and I'd like to submit
a couple of issues about musicxml2ly on the bug tracker.
I followed the Bug Squad Setup guide, here is my sourceforge username
