Re: musicxml2ly produces unexpected EOF in .ly file
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 misread. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: musicxml2ly produces unexpected EOF in .ly file
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 . There's something wrong: $ file jafanosumu.ly jafanosumu.ly: data There's some bad encoding. See attached file. $ ls -lh ~/.local/lilypond/usr/bin/python* -rwxr-xr-x 2 fede fede 5,1K 24 giu 14.11 /home/fede/.local/lilypond/usr/bin/python -rwxr-xr-x 2 fede fede 5,1K 24 giu 14.11 /home/fede/.local/lilypond/usr/bin/python2.4 It's just my installation? 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. That would explain why the conversion only fails with manually downloaded version of lilypond, which bundles python 2.4.5. When I hand edit the musicxml2ly script, forcing it to use the system python version (2.7.13), the result file looks well encoded. $ file -i jafanosumu_converted_using_python2.* jafanosumu_converted_using_python2.4.5.ly: application/octet-stream; charset=binary jafanosumu_converted_using_python2.7.13.ly: text/plain; charset=us-ascii ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
musicxml2ly produces unexpected EOF in .ly file
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 following error: "syntax error, unexpected end of input, expecting \header". Here is the full output: https://hastebin.com/raw/navufewufu And the musicxml file content: https://hastebin.com/jafanosumu.xml This error happened with any musicxml file I tried to convert from Musescore. After some research, I found this topic on the lilypond-user list http://lilypond.1069038.n5.nabble.com/XML-to-ly-and-Lilypond-again-td203101.html which looks like exactly the same. The suggested workaround (replacing split_string_and_preserve_doublequoted_substrings by string.split in musicexp.py:139) makes it work, but I'm wondering if I'm doing something wrong. Victor ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Subscribing
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 : vicrou Don't hesitate to get in touch if you need further information. Regards, Victor ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
