musescore / musescore/MuseScore

Kerning issue with older font in exported PDF

Open
#24,904 4 comments 0 reactions 3 assignees View on GitHub

Nobody has claimed this yet.

engraving P3 Qt-next
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. 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
  • 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.