musescore / musescore/MuseScore

Incorrect Appearance of Bolded Fonts in a Font Family

Open
#34,486 0 comments 0 reactions 2 assignees View on GitHub

@miiizen is already working on this.

Since Aug 7, 2026.

engraving P2
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
  1. Select a font that has a family with multiple weights/styles (Here is Sitka - Sitka Text);
  2. Type anything (Here is under Tempo text. So far the problem has been seen in text type Tempo text, Title, Expression/Staff text — likely affects all text elements) and have it bolded by toggling tab "Properties";
  3. Notice: When the zoom level ≤202% (Fig. 2 & 3), the characters are added with an outline; when greater, the outline disappears (Fig. 4). The appearance characters' with an outline doesn't match their expected "Bold" style (Fig. 4, captured in Windows 11 notepad).
  4. See also issues #31602, #33693.
Supporting files, videos and screenshots

ImageText un-bolded.

Image *Zoom Level = 159%, can be seen at the bottom-right corner of the window, ditto.* Image *Zoom Level = 200%.*

ImageZoom Level = 202%.

Image
In which versions of MuseScore Studio is this issue present?

4.7.4.260706075

Regression

I was unable to check

Operating system

Windows 11 Home Edition 25H2 Version 26200.8973

Additional context

In other word-processing app, all the weights appear but in MuseScore it's not.

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.