musicxml2ly makes an apparently defective lilypond file

[Patrick Karl]

So, I have the following lilypond file, named test.ly:

\version "2.19.46"
music = { c'' }
\score {
  \new Staff \music
  \layout { }
  \midi { }
}

I compile it so:  lilypond test.ly

which generates a pdf file and a midi file.

I open the midi file in Musescore 2.0.3.1 and export an xml file, named test_midi_Musescore.xml

I run musicxml2ly test_midi_Musescore.xml, which generates a lilypond file named test_midi_Musescore.ly.

There seem to be two problems with the output of musicxml2ly:

  *  file test_midi_Musescore.ly produces: test_midi_Musescore.ly: data

      It should probably produce:  test_midi_Musescore.ly:  ASCII text.  Another indication that something is aglee with test_midi_Musescore.ly is the output of "more test_midi_Musescore.ly", namely:  "test_midi_Musescore.ly" may be a binary file.  See it anyway?

  *  lilypond is unable to compile test_midi_Musescore.ly.  It fails with

pat$ lilypond test_midi_Musescore.ly
GNU LilyPond 2.19.46
Processing `test_midi_Musescore.ly'
Parsing...
test_midi_Musescore.ly:6:25: error: EOF found inside string
    encodingsoftware = 
                        "
test_midi_Musescore.ly:6:25: error: syntax error, unexpected end of input, expecting \header
    encodingsoftware = 
                        "
fatal error: failed files: "test_midi_Musescore.ly"

I am attaching test.midi, test_midi_Musescore.ly and test_midi_Musescore.xml.

Is there a workaround?  Is this a bug?

test.midi
Description: MIDI audio

test_midi_Musescore.ly
Description: Binary data

test_midi_Musescore.xml
Description: Text Data