I'm currently writing a programme to convert the MusicXML exported by MuseScore into PMW code, so I can print customised key signatures, and a few other things. Hence, anything missing in the xml exported code will mean lost effort; I mean, I use MuseScore during the composition / arrangement phase, but for preparing the ultimate, printable version I need to transfer the whole of what I did into PMW for further processing. That's the whole idea of XML in the first place, isn't it?
Now, I noticed the following (so far...):
1) Accidentals, apart from flats and sharps, are never exported. An empty element is there alright, but with no accidental specification.
2) Clef changes appear where cautionary clefs are put, i.e. at the end of the preceding meaure. It appears that the MusicXML specification does not impose any rules here, but wouldn't it be more logical to put the clef change where it starts to be effective, and leave the cautionary clefs for the importing programme to worry about? So, when a measure starts with a new time signature AND a new clef, why is time signature change put at the stat of the concerned measure, but not the clef change? Shouldn't they be contained within the same element at the start of that measure?
3) Although double tremoloes are displayed on screen, they're never exported to XML; only single tremoloes are.
4) Is there a way in the MusicXML specification to distinguish between system text (like tempo changes) and text that applies to the staff that happens to be at the top of the system? So, for example, a "rall." concerns every staff in the system, but a "sempre pizz" on the Vn I staff of a string quartet should only concern the Vn I player, and should not be replicated on other staves when each of them is extraced.
Note: I only posted this after I found nothing about the above points in the Issue Tracker's xml search results.
Many, many thanks.
Hosam Adeeb Nashed