musescore / musescore/MuseScore
Chord symbol "ré" not correctly recognized in French notation
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
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
Description:
When using French chord notation, entering the chord symbol "ré" (for D) partially fails. MuseScore correctly replaces "re" with "ré", adding the accent on the letter "e", but it neither capitalizes the "R" nor recognizes the text as a chord symbol. Therefore, it isn't played as a chord during playback, nor does it transpose correctly. All other French chord names (Do, Mi, Fa, Sol, La, Si) are recognized correctly. This issue might be related to the acute accent on "ré".
Steps to reproduce:
-
Open MuseScore and create a simple piano score.
-
Change chord notation to French by going to:
Format → Style → Chord Symbols → Appearance → Notation → French -
Insert a chord symbol by pressing Ctrl + K.
4.Type "re" and press Enter.
Result:
MuseScore converts "re" to "ré", correctly adding an acute accent to "e", but does not capitalize the "r" nor interpret it as a chord symbol.
As a result:
The chord isn't played back.
It doesn't transpose with the score.
All other French chord names function as expected.
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/6fc6ef78-4bd0-4270-ae07-40125dd6d161
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.5.2-251141402, revision: github-musescore-musescore-ac9d3bc
Regression
I was unable to check
Operating system
Windows 11
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.