musescore / MuseScore

MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
https://musescore.org
Other
12.12k stars 2.62k forks source link

Kerning issue with older font #24904

Open rpatters1 opened 7 hours ago

rpatters1 commented 7 hours ago

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

  1. Install the attached font. This is an old font created in Fontographer in the 90s using Times Bold as the base glyphs (though this font is Regular). I migrated it to .otf about ten years ago.
  2. Set this as the Tempo text style in a MuseScore document (or open the sample document below).
  3. Insert a tempo of "Tempo de cucaracha" in the document (or use the sample document below).
  4. Export the first page to PDF or use the Apple Print Dialog to generate the PDF.

You will see the "uc" in "cucaracha" is incorrectly kerned. (This is a screenshot of a MuseScore-generated PDF, but the effect is even more noticeable on a physical printout.)

Screen Shot 2024-09-24 at 8 38 27 AM

Finale does not exhibit this problem in either method of creating PDFs, nor do Word nor Pages. The following examples are screenshots of PDFs created by these programs.

Finale:

Screen Shot 2024-09-24 at 9 01 25 AM

Word:

Screen Shot 2024-09-24 at 8 45 07 AM

Pages:

Screen Shot 2024-09-24 at 8 47 35 AM

FWIW: Dorico also exhibits the problem.

Supporting files, videos and screenshots

Patmm.otf.zip LaCucaracha-sample.mscz.zip

What is the latest version of MuseScore Studio where this issue is present?

4.4.2

Regression

I was unable to check

Operating system

macOS 12.7.6

Additional context

No response

Checklist

cbjeukendrup commented 6 hours ago

FWIW: Dorico also exhibits the problem.

That's interesting, then it's probably a Qt bug. I couldn't find anything that's unambiguously related to it in Qt's bug tracker though. Anyway, we're most likely going to update to the latest Qt version relatively soon, so we'll see if it has been fixed by chance.

rpatters1 commented 6 hours ago

I had the same thought that it might be a Qt bug.