I see this issue is quite old, but I can confirm the (mis)behavior is still present in version 1.3 revision 5702 (being used on OS X 10.9.3).
I poked around briefly in the uncompressed XML file format to see if there was anything obvious I could do to fix it outside of the application, but recoiled in horror when I saw that there were local, explicit, full < html >...< /html > snippets (including, of all things, < table >s!) for each fingering annotation. Alarming. It seems so brittle, by design, that I'm now wary of investing any time inputting any information into musescore at all.
You'll be happy to hear all the explicit html encoding will be gone for 2.0. Definitely try out a Nightly build - keeping in mind of course this is still experiment/pre-release/not-meant-for-real-production-use software. It's pretty stable though and you can get a very good feel for how it will look. Text styles now work as you might expect from experience with Word or whatever - change the style, and all elements with that style automatically update. No explicit formatting is normally written to the file except if you customize a particular element to deviate from the normal style, and even then, it's much less "brittle" than 1.3 (I would note, though, that as distasteful as the html in the file *looks*, it actually *worked* just fine, as long as you didn't need the formatting to update when you changed the style settings).
Comments
MuseScoreNightly-2013-07-15-2009-c4e95c7.7z
I see this issue is quite old, but I can confirm the (mis)behavior is still present in version 1.3 revision 5702 (being used on OS X 10.9.3).
I poked around briefly in the uncompressed XML file format to see if there was anything obvious I could do to fix it outside of the application, but recoiled in horror when I saw that there were local, explicit, full < html >...< /html > snippets (including, of all things, < table >s!) for each fingering annotation. Alarming. It seems so brittle, by design, that I'm now wary of investing any time inputting any information into musescore at all.
Hi plboerboom
1.3 will no longer receive fixes - do you want to try a nightly build, or the source code for 2.0?
You'll be happy to hear all the explicit html encoding will be gone for 2.0. Definitely try out a Nightly build - keeping in mind of course this is still experiment/pre-release/not-meant-for-real-production-use software. It's pretty stable though and you can get a very good feel for how it will look. Text styles now work as you might expect from experience with Word or whatever - change the style, and all elements with that style automatically update. No explicit formatting is normally written to the file except if you customize a particular element to deviate from the normal style, and even then, it's much less "brittle" than 1.3 (I would note, though, that as distasteful as the html in the file *looks*, it actually *worked* just fine, as long as you didn't need the formatting to update when you changed the style settings).