musicxml2ly.py conversion errors (two)

[Ken Kellogg-Smith]

LilyPond version:                v2.14.1
musicxml2ly.py file date:     6/12/2011
operating system:               Windows XP 2002 SP2
text editor:                          jEdit

    I experimented with musicxml2ly by downloading a MusicXML-coded lead sheet 
(Scott Joplin's "The Entertainer" ) from the Wikifonia website 
(www.wikifonia.org).  I used the resulting .ly file with LilyPond to create 
the .pdf sheet music file.  I then reviewed musicxml2ly .ly source code, and 
compared the LY .pdf output file to the outputs of the download file generated 
by Finale Reader, museScore, and Wikifonia (Ghostwriter pre-release v8.57).   
Both musicxml2ly output files looked fine, but I did find two discrepancies.  
One of the discrepancies affected the music notation in the .pdf file, and the 
other only affected  the output .ly source code itself.  The discrepancies are 
as follows:

1.  .ly source code:   Internal measure numbering errors beginning at (jEdit) 
line 30 et. seq. 
musicxml2ly's measure numbering routine made two related discrepancies:
     (1) at line 30: measure #1 was identified as measure number #2,
     (2) at line 36: the measure number was duplicated (measure number "5" 
repeated). 
     (Note:  These two discrepancies are 'cosmetic' and had no impact on 
the .pdf output file.  In fact, the second error "self-corrected" the initial 
measure numbering error in the .ly source code caused by the first error.)

2.  .ly source code:  At (jEdit) line 61: the text "Fine" is incorrectly put 
in measure 22 instead of measure 21.
This discrepancy directly impacted the appearance of the .pdf output file.
The correct location of the "Fine" text is measure 21, where according to the 
comparison programs it looks like the download file's arranger put it.  
Although Wikifonia's output file has the text written above the line in the 
score denoting repeat #2, Finale Reader and museScore both display that text 
under the line for repeat #2, above the staff, and right justified.

The work being done on writing and testing musicxml2ly is very, very  
impressive!  I hope my twi small findings will help a little.

Very best regards,

Ken Kellogg-Smith