musescore / musescore/MuseScore
sff uses a non-SMuFL, Leland-specific ligature and breaks with other fonts
@miiizen is already working on this.
Since Sep 18, 2026.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Engraving bug (incorrect score rendering)
Description with steps to reproduce
An sff dynamic renders as one ligature with Leland, but as two separate glyphs ("sf" + "f") with Bravura and other SMuFL fonts. Leland provides a font-specific codepoint (U+F631) for this glyph, which is not in the SMuFL spec.
sfff and sfffz are affected too, and render with a gap even with Leland, since Leland doesn't have private glyphs for those either.
Suggest constructing sff/sfff/sfffz in a SMuFL-compliant way (i.e. from the standard s, f, z glyphs/ligatures already in the spec) rather than depending on a font-specific precomposed glyph, so it renders consistently regardless of the chosen music font.
See also this comment in #34910.
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
Nightly main
Regression
No.
Operating system
macOS 26.6.2, Ubuntu 24.04.4 LTS
Additional context
No response
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.