Overture import can include unescaped ampersands.

• Jan 20, 2015 - 04:47
Reported version
2.1
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

1. Open a .ove file in MuseScore then save as .mscz(.mscx) format. Close MuseScore.
2. Run MuseScore again.
3. Open .mscz file saved before.

A load error window was shown:
Cannot read file :
bad format

Attachment Size
Blue Danube.mscz 33.29 KB

Comments

• Jan 20, 2015 - 07:07
Title MuseScore file problem ⇒ Overture import can include unescaped ampersands.
Status (old) active ⇒ needs info

The console output pinpoints the problem - an unescape ampersand in one of the instrument names. The question is, would this still happen if the original overture file were imported with a current build. So indeed, we would need the original file.

Reply

• Jan 20, 2015 - 07:42

Hmm, ISTR there had been a fix related to that post Beta 2?
Maybe 3e673e2 ?

For the record, here's the console output (or a debug build):
Debug: htmlToString: read token: Invalid (...\MuseScore\libmscore\xml.cpp:668, QString Ms::XmlReader::readXml())
Debug: Blue Danube: xml read error at line 208 col 38: (...\MuseScore\libmscore\scorefile.cpp:1160, bool Ms::Score::read(Ms::XmlReader&))

Attached the fixed file...

Attachment Size
Blue Danube.mscz 32.17 KB

Reply

• Jan 20, 2015 - 14:21

Yes, there was a fix that provides the capability of automatically espacing ampersands in text. What I don't know is if the Overture import uses this facility where it would need to. Similar question for other non-native formats.

Reply