There were some specific "hacks" in the glyphnames.json, to address directly some symbols in the font while for Bravura and in "pure SMuFL" these symbols are composed. Unfortunately, some symbols are missing in MScore to do the composition and so are indeed composed with the bravura ones. The missing ones seems to be
ornamentMiddleVerticalStroke
ornamentBottomLeftConcaveStroke
ornamentBottomRightConcaveStroke
ornamentLeftVerticalStroke
ornamentTopRightConvexStroke
Also, the others might need to be checked so they overlap correctly...
Comments
Is it the new fallback that causes this?
It's a mix... It's my change to use a single glyphnames.json https://github.com/musescore/MuseScore/commit/9ef2f130e286ccf78130f1e42…
There were some specific "hacks" in the
glyphnames.json, to address directly some symbols in the font while for Bravura and in "pure SMuFL" these symbols are composed. Unfortunately, some symbols are missing in MScore to do the composition and so are indeed composed with the bravura ones. The missing ones seems to beAlso, the others might need to be checked so they overlap correctly...
Fixed in branch master, commit 64672e9e50
fix #125546, fix #125436, fix #125246, fix #125186: update mscore font
Automatically closed -- issue fixed for 2 weeks with no activity.