Saving xml vs mscz
I'm reproducing snippets of scores to be included in HTML files. In mscz, I set the height, width, and margins to cropped, uploadable dimensions that can be immediately imported into the HTML. I send the mscz files AND xml files on to the post processer who is compiling the HTML.
The mscz files open perfectly, and import perfectly. The xml files open with the deleted header back in place, showing instruments I've hidden, and generally wrong dimensions. Is there something I am supposed to be doing to make the mscz and xml files match exactly?
| Attachment | Size |
|---|---|
| score_p138a AUDIO.mscz | 9.79 KB |
| score_p138a.xml | 15.98 KB |
Comments
One of the reasons MuseScore has its mscx/msxz file format is because MusicXML doesn't allow for containing all types of layout information in it.
If dimensions matter for your HTML publishing, consider exporting the score to one of the image formats instead.
In reply to One of the reasons MuseScore… by jeetee
I'm saving and exporting png files with the audio, xml, and msxz files. The program files are sent so the post processor can verify how the audio and png files were created. It's the audio and png files that are actually imported into the HTML. They look and sound fine.
Thanks jeetee for explaining the limitations of xml and why MuseScore has it's own language. :)
XML is a fine format for sharing the basic information in a score with others who use other applications, but it doesn't contain all the information used by MuseScore (or any other notation program). There is no way to have them match exactly, they simply contain different types of information. Just as a Japanese translation of an English text will never match exactly, and attempting to translate to Japanese and then back will seldom result in anything close to the original.
In reply to XML is a fine format for… by Marc Sabatella
Thank you, Marc. I understand now. I'll include the XML files because they are nearly universal, but I'm depending on MuseScore and exported pngs to portray what's needed for an accurately reproduced HTML. Another book for Distributed Proofreaders on it's way to Project Gutenberg.
Thanks again! :)