musescore / musescore/MuseScore
Hyphens engraving in lyrics, after a system or page break, is not uniform
Nobody has claimed this yet.
- 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
After downloading the 4.4.3 version, I checked some old scores created months ago with an older version of MS.
This is the pdf of the original version of the score:
Cantique de Noël.pdf
I want you to focus on the hyphens.
This is the score after downloading the version 4.4.3 (I know the hyphens spacing was changed, #24621).
Cantique de Noël.zip
Check the first syllable in measure 3, 9, 11, 13, 17, 19, 21, 23, 25, 27.
I agree with having a hyphen before the syllable after a section break, this way you know that that is a syllable and not a new word, but every instance of a hyphen after a section break has a different engraving: every time, the distance between the hyphen and the syllable is different, like the size of the hyphen itself.
I think that the best solution here is a uniform engraving for every istance.
Supporting files, videos and screenshots
What is the latest version of MuseScore Studio where this issue is present?
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.3-242971445, revision: github-musescore-musescore-eb6b367
Regression
I was unable to check
Operating system
Window 10 Pro
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.