Text from 1.x score becomes styled in 2.0, even if it had been changed from it's default size or font
Text (well, at least lyrics) from 1.2 score becomes styled on 2.0, even if it had been changed from it's default size
So if in a 1.2 score you change the text size away from the default (that corresponds to 'space' setting of the score), that change get's lost when opening the score in 2.0 (here: e059b3a)
I haven't tested, but would guess that the same happens with changed fonts.
Comments
"So if in a 1.2 score you change the text size away from the default (that corresponds to 'space' setting of the score)..."
What does this mean? It can't be right that the text size corresponds to the 'space' setting. They're completely different numbers.
They are different numbers but relate. If you chage the size of a space, you change a whole bunch of other default sizes along with it.
This in itself is OK, but it is not IMHO, when having changed sizes away from their default.
I can no longer reproduce, but I'm not totally clear on the steps, either. If you can still reproduce, could you post a sample score?
Only place where I see an issue with dynamics and repeat text, since those are not treated as plain text but are instead rendered using the score font. See #13019: Text style not honored for dynamics, segno, or coda.
In 1.3 add lyrics to a score
Right click a syllable, text properties, increase size, tick 'apply to all similar'
Save. Open in 2.0
Size of lyrics is back to whatever the style setting is active, but not the size set in 1.3
Hmm, I still can't reproduce, latest master (c24022f) on Ubuntu Studio 14.04.
Here is the test file I am using. Opens exactly the same in 2.0 as in 1.3 as far as I can tell. I tried both lyrics and staff text, changes to font as well as size, changes to just part of the text (using the text toolbar) versus changers to whole element (using text properties) - in all cases it works as expect. Could you post the score that is not working for you? I assume something must be different about it.
I can't reproduce either anymore
Thanks for verifying. I am pretty sure this was addressed during a big round of text implementation changes a few months ago, but I thought I would ask to be sure closing it myself.
Automatically closed -- issue fixed for 2 weeks with no activity.