Changing Text in lines leads to corruption.

• Apr 17, 2018 - 23:00
Reported version
2.2
Priority
P2 - Medium
Type
Graphical (UI)
Severity
S5 - Suggestion
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore
Tags
2.3

This was discovered in version 2.2.1 but exists in 2.1 with a slight variation.

Create a line in a score
Make the Begin text read
Save the score
Close and reopen the score

Result: Load error XML read error at line ### column ###: sym
Expected result: MuseScore realized the text is illegal and does not accept the change.

The slight variation in 2.1 is that you actually get a little bit of visual feed back like this:
ottava error.png

This does not appear in version 2.2.1. I suspect this was changed as part of #178591: Ottava style in General Style dialog not consistent though I have no proof.

See https://musescore.org/en/node/271491 for files where problem was found and fixed one time for the user.

Comments

• Apr 17, 2018 - 23:34

I'm guessing you originally included the text to use, but it seems to have been interpreted at HTML or Markdown as it isn't displaying. Can you describe the text? I might guess it's something involving an ampersand?

Reply

• Apr 18, 2018 - 07:17

You can make this render here by adding an <xml> before and a </xml> after, e.g. the broken code here is:

          <beginText>
            <text><sym></text>
            </beginText>
 

Reply

• Nov 2, 2018 - 11:37
Severity S2 - Critical ⇒ S5 - Suggestion
Priority ⇒ P1 - High
Regression ⇒ No
Reproducibility ⇒ Always
Workaround ⇒ No

Suggestion sounds like "Support reading xml/html tags in the text everywhere in MuseScore", right?

Reply

• Nov 2, 2018 - 12:04

Well, it is also about the possibility to render a score unreadable by adding some text that may look like an (unclosed) HTML/XML tag
like e.g. <sym>

It doesn't do that in master though, it just turns into an empty string. And ever works properly with something like <sym>accidentalFlat</sym>, at least it does for text lines (which this issue is about. So I guess we can close it?

Reply

• Nov 2, 2018 - 14:14

It works already, it just accepts such HTML/XML tags (but shows them as an empty string,.i.e. ignores them, just like every browser does or should do)
If you really want < and > being shown as text this would be another issue

Reply