musescore / musescore/MuseScore

Unicode characters can't be inserted into lyrics boxes

Open
#24,897 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P2 regression MS4 UX/interaction
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
  1. Add notes
  2. Begin to add lyrics.
  3. Use Unicode Hex Keyboard
  4. Attempt to enter character
  5. "No Note selected" message pops up.
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/03d8f8a7-f0d6-419e-b79c-9a420242e04c

unicode_mwe.mscz.zip

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

4.4.2

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

macOS 15.0 Sequoia

Additional context

I probably should have reported this earlier but did not. I've had this issue since at least 4.1 on macOS Ventura 13.4.1.

The problem is that (for example) Latin texts, particularly ecclesiastical Latin with Gregorian chant in modern notation, depend on accented letters available with Unicode but not the basic keyboard (e.g. the glyph in question ǽ (U+01FD) as syllabic accentuation is not absolutely determined by the number of syllables particularly in words of three syllables, to say nothing of languages where there is nothing optional about the diacritic or accent mark.

A related trouble is that copying and pasting moves the cursor to the next note (syllable). This is also infelicitous, but could be ignored if Unicode entry were to be supported again.

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.

Research direction

Reproduce the issue on macOS using MuseScore Studio 4.4.2 and the attached unicode_mwe.mscz example. Start by tracing lyrics-box input handling for Unicode Hex Keyboard entry; done means accented Unicode characters can be inserted without the “No Note selected” message, while the separate copy-and-paste cursor behavior may remain out of scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.