`ornamentMordentInverted` vs `ornamentMordent` vs. `ornamentShortTrill`

[Jojo-Schmitz]

Apparently aa2b7b7 got rid of ornamentMordentInverted and replaced it with ornamentMordent which in turn got renamed to ornamentShortTrill.

• Now how to deal with scores prior to that change? While the replacement of ornamentMordentInverted (to ornamentMordent) can get handled, the rename of ornamentMordent (to ornamentShortTrill) can't (as there is no way to tell whether it is the old or the new), at least I don't see how? (Well, for MuseScore I have a solution for this now)
• And how would scores using the newer version be read by older applications, they'd loose the ornamentShortTrill, no way to render it as their ornamentMordent.

Looking at the commit message for aa2b7b7 I don't see any reason why this got changed, none of the issues that commit is supposed to fix deals with mordents?

Shouldn't ornamentShortTrill rather be ornamentPrallTrill?

[Jojo-Schmitz]

No comment on this since 3 months?

[Jojo-Schmitz]

Still no comment half a year later?

[dspreadbury]

I've not had time to look into this issue yet, but I will do so when I next have time for concentrated work on SMuFL. I'm sorry to keep you waiting.

[Jojo-Schmitz]

Thanks!

[dspreadbury]

The specific change to those glyph names predates commit aa2b7b7, which was the first commit after SMuFL moved to the W3C in which the Gitbook specification pages were updated. Unfortunately I can't easily put my finger on the original change, but I can explain it.

In the UK many people (myself included) learned about Baroque and classical ornaments through the tuition of the ABRSM, and their theory books show the mordent as the glyph now named ornamentShortTrill in SMuFL, and the glyph now known as ornamentMordent as an "inverted mordent". The ABRSM's tuition is, I think it's now fair to say, idiosyncratic, but because it's drilled into us so much, I accepted it without question. So the initial versions of SMuFL had this wrong, and to put things straight ornamentMordent became **ornamentShortTrill**, **ornamentInvertedMordent** become **ornamentMordent**.

To deal with this in Dorico, for example, we automatically fix up projects on loading if they pre-date this change.

[Jojo-Schmitz]

Thanks, I guess we'd need to the same then for MuseScore. We've recently started doing something like this for some other changes that need this kind of compatibility.

[dspreadbury]

OK. I'll close this issue for now.

[Jojo-Schmitz]

Yes, thanks, it's been sufficiently explained now.
Back to the drawing board on implementing a backwards compatible "import"...

Oops, actually this is exactly what I did already, somehow I managed to confuse myself ;-)