musescore / musescore/MuseScore

Failure to use true italic font variant

Open
#21,726 2 comments 1 reaction 2 assignees View on GitHub

Nobody has claimed this yet.

engraving needs info text
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)

Bug description

Using italics in standard Times New Roman results in a false, synthesized slanted version of Times New Roman, rather than the true italic version, even though the latter is installed by default on Windows, and recognized as such by other Windows applications such as LibreOffice Writer.

This error occurs with many other system fonts (e.g. Bodoni MT), as well as several non-system fonts (e.g. Source Serif), making this issue rather severe as it makes a large number of fonts nigh-unusable for expression text, bar numbers, or alternate-language lyrics. It does not occur with all system fonts -- for example, Gentium Basic gets correct italics.

Steps to reproduce
  1. Open an empty MuseScore Score
  2. Set the title and subtitle to font Times New Roman, and the subtitle to italic, in the Properties panel.
  3. Observe that the subtitle does not look like Times New Roman italics
Screenshots/Screen recordings

Italics as they incorrectly appear in Musescore 4.2.1:
Musescore bug italics 1
Italics as they correctly appear in LibreOffice and most other applications:
Musescore bug italics 2

MuseScore Version

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433

Regression

I don't know

Operating system

Windows 10 & 11

Additional context

I'd categorize incorrect text font rendering as an engraving bug; apologies if this isn't true here.

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.