musescore / musescore/MuseScore

[UI/UX] Unnecessary shortcut keys (mnemonics) displayed in the macOS menu bar

Open
#33,034 5 comments 2 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Jul 23, 2026.

P2 strings UI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

In MuseScore Studio on macOS, menu bar items incorrectly display Windows-style mnemonics (e.g., (F), (E)).

Crucially, this issue specifically occurs when the application language is set to Japanese. These notations are not used in macOS native applications and do not function as shortcuts on this OS, making the UI feel non-native and cluttered.

Image

Steps to reproduce

Launch MuseScore Studio on macOS.

Set the display language to Japanese.

Observe the system menu bar at the top of the screen.

Notice the suffixes like ファイル (F), 編集 (E), etc.

Expected behavior

The menu bar items should follow macOS Human Interface Guidelines. For the Japanese locale, it should only display the menu title (e.g., ファイル, 編集).

Actual behavior

The menus are displayed with mnemonics:

ファイル (F)

編集 (E)

表示 (V)

...and so on.

Environment

OS: macOS

App Version: MuseScore Studio 4.x

Language: Japanese (Confirmed this does not occur in the English default setting)

Supporting files, videos and screenshots
Image Image
In which versions of MuseScore Studio is this issue present?

4.6.5

Regression

I was unable to check

Operating system

macOS 15.7.3

Additional context

The issue appears to be caused by the Japanese translation source file:share/locale/musescore_ja.ts

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.