musescore / musescore/MuseScore
[Musicxml Export] - Better export of text frames
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
Other type of issue
Bug description
No response
Steps to reproduce
Please see this score:
https://musescore.com/user/4887176/scores/10107529
All text frames on the top staff are for variation numbers. When exported, they becomes credit texts, and if the variation number is at the middle of a page, thus the beginning of a middle system, then it's impossible to know if the credit word is for the first system or others. When translating in braille, this becomes a big problem. So if applying Musicxml 4.0, a system only-top property can be applied to all text frames at the topmost staff, and only-bottom applies to the text frames of the last staff.
Screenshots/Screen recordings
No response
MuseScore Version
4.0.2
Regression
No.
Operating system
All
Additional context
No response
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.
Research direction
Start with the MusicXML export handling for text frames and compare its output with the linked score. Check how MusicXML 4.0 represents only-top and only-bottom system text, then verify that variation numbers are distinguishable when translated to braille.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100