Filename problem when generating a compressed MusicXML file
Observed on MuseScore 5.6.2.x
When we ask MuseScore to generate a compressed MusicXML file (*.MXL), if the MXL filename (whether inherited from the filename of the source score or entered or edited by the user) contains an "&", the MXL file (although cheerfully created) is misformed, and cannot be opened by MuseScore, Overture, or other MusicXML-aware programs.
That character should be valid under the norms for filenames in Windows or MacOS.
This is hardly a big or widespread problem. But I thought I would report it.
Doug
Comments
.
here's no MuseScore 5.6.2, I assume you mean 3.6.2 ;-)
This is a (meanwhile) known issues see #321376: [MusicXML import] Musescore cannot open MusicXML file it created if filename contains an ampersand
In reply to here's no MuseScore 5.3.2, I… by Jojo-Schmitz
Hi, jojo,
>>there's no MuseScore 5.3.2, I assume you mean 3.6.2 ;-)
I actually said "5.6.2", which of course is wrong. Yes, I should have said "3.6.2".
>>This is a (meanwhile) known issues see #321376: [MusicXML import] Musescore cannot open MusicXML file it created if title contains an ampersand.
Thank you so much for that cite.
This is of course not a debilitating anomaly.
Doug
In reply to Hi, jojo, >>there's no… by Doug Kerr
oops, corrected.
And just learned a new word ;-)
In reply to Hi, jojo, >>there's no… by Doug Kerr
Problem found and fixed...
Won't help for imporing files that are broken already, but will prevent them from breaking on export
In reply to Problem found and fixed… by Jojo-Schmitz
Hi, jojo,
Lovely!
Thanks so much.
Doug
In reply to Hi, jojo, Lovely! Thanks so… by Doug Kerr
You can get a fixed 'development' version from github