Musicxml Export - Composite Dynamic expressions export different garbage codes

• Dec 25, 2018 - 07:57
Reported version
3.0
Type
Performance
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
MuseScore
Tags
musicxml

Hello,
When I doing braille transcriptions of Musescore files, I always encounter this problem. Sometimes there are expressions such as "p dolce". These are exported as other-dynamics, no problem. But:
1. Before Musescore 3, the dynamic p, f, m, z etc are exported as tag within other-dynamics, with html code for lt and gt. So I have to make manual replacement to get correct braille result.
2. Now with Musescore 3, this is changed, not better, but worse. All dynamic letters are changed to unknown unicodes, which can't be judged and make correct braille transcription.
So, can the future Musescore just export these dynamics within text block as plain dynamic letters? These unicodes can only be used in Musescore, not interchangeable with other softwares, including braille transcription. Thank you in advance!

Regards
Haipeng

Comments

• Sep 8, 2019 - 11:13

Thanks, this is a better solution. You can also put "p dolce" as just one piece instead of splitting it into two, in case there are lots of them such as "sempre pp al fine". THe code will be clean, and the software knows how to convert them into braille.

Reply

Fix version
3.3.0