musescore / musescore/MuseScore

Poor Padding around Forte Characters

Open
#26,537 1 comment 2 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P4
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

Please improve the padding around the forte marking families (f, ff, fff, sf, etc). In the last line of text in the example, it looks like there is no space between "4 ft." and ff, and then two spaces after ff, when there is actually the usual single space on either side.

Supporting files, videos and screenshots

Image

https://github.com/user-attachments/assets/cfe45092-9109-40bc-a2a6-841f8ad3f51d

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

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670

Regression

I was unable to check

Operating system

Windows 11

Additional context

If I was to be picky, it is a little irritating that the equals signs in the second and third lines of text are not perfectly aligned, even though the ff and p markings are in acceptable positions. Word processors have options to add a hair space or thin space, but as far as I am aware, there is no option for that in Musescore.

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.