RE: Working on issue 665, how to proceed?

[lilypond]

I followed your suggestion and added a the filename to the output, also now it 
is possible to use no header.

 

Further the resulting filename is defined in the musicxml.ly, and is 
<basename>.xml if the function is called with a music expression as argument,

and is <basename>-score.xml if you call the function with a score as argument. 

I think the jaap-test-01.xml file you have is the result from your earlier try, 
when you used {R1} as an argument to the function.

 

Jaap de Wolff

 

Van: Thomas Morley <address@hidden> 
Verzonden: Sunday, November 17, 2019 12:20 PM
Aan: address@hidden
CC: Jacques Menu <address@hidden>; Urs Liska <address@hidden>; lilypond-devel 
<address@hidden>
Onderwerp: Re: Working on issue 665, how to proceed?

 

 

 

Am So., 17. Nov. 2019 um 11:49 Uhr schrieb <address@hidden 
<mailto:address@hidden> >:


When I use your example on 2.19, I get the same error

When I add 
\header {} 
to it, it creates a file named test.xml 

 

I tried this. At first attempt I've got: 

While evaluating arguments to music->musicxml in expression (music->musicxml 
score porttype):
/home/hermann/de-wolff-lilypond-git/build/out/share/lilypond/current/scm/musicxml.scm:2319:41:
 Unbound variable: porttype

 

Likely a typo in this line

((ly:score? score) (music->musicxml score porttype)))))

->

((ly:score? score) (music->musicxml score port type)))))

 

Furthermore, apart from jaap-test-01-score.xml I've got an empty file called 
jaap-test-01.xml

An intermediate file?

 

The terminal displays:

GNU LilyPond 2.21.0
Processing `jaap-test-01.ly <http://jaap-test-01.ly> '
Parsing...
generating and writing musicxml
remove first backup elements
reposition end barlines
remove empty items
order items
update header

done writing musicxml
Success: compilation successfully completed

 

I'd suggest to display the name of the file which is generated. 

Probably implement a way the user can put-in a custom-name for the .xml-file.

 

Nevertheless these are thoughts for some final polish, let me dig a bit deeper 
into your code.

Alas, my time is very limited nowadays ...

 

 

Cheers,

  Harm