MuseScore generates unparseable MusicXML for ampersands in chord names
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
See the attached .mscz file, which includes the ampersand character ("&") in a chord name. When exporting this as MusicXML, the resulting XML (also attached here) cannot be parsed by an XML parser because the ampersand isn't escaped.
The solution is to escape the ampersand as "&" in the MusicXML. MuseScore already does this in other places (e.g., system text).
| Attachment | Size |
|---|---|
| ampersands.mscz | 4.51 KB |
| ampersands.musicxml | 17.25 KB |
Fix version
3.5.0
Comments
Rather as "&", guess you meant that?
Relates to #270643: [EPIC] MusicXML import/export issues
In reply to or as "&" by Jojo-Schmitz
Yes — sorry. Looks like this issue tracker also needs to auto-escape input. :)
Fix implemented, will create a pull request.
Pull request https://github.com/musescore/MuseScore/pull/6256
Fixed in branch 3.x, commit 870db63869
fix #305313: MuseScore generates unparseable MusicXML for ampersands in chord names
Automatically closed -- issue fixed for 2 weeks with no activity.