Staff text line, System text line, and Change instrument palette items should translate

Open Beginner friendly

#34,712 opened on Aug 26, 2026 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 68/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Active
Tech stack: cpp
Domain: localization

Research direction

No source files, tests, or entry points are named in the issue. Start by locating the palette item labels and their translation entries, then verify the Staff text line, System text line, and Change instrument labels use translatable, consistent wording in the UI.

Written by the indexing model from the issue text.

Description

engraving P3 UI

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

There is a weird inconsistency in naming between the "Stave text" and "Staff" text palette items.

Their hover text is "Stave text" and "Stave text line" respectively.

Supporting files, videos and screenshots

In which versions of MuseScore Studio is this issue present?

OS: macOS Sequoia (15.7.7), Arch.: arm64, MuseScore Studio version (64-bit): 4.7.4-260706075, revision: github-musescore-musescore-7688c00

Regression

I was unable to check

Operating system

macOS

Additional context

My region settings:

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

Dominant language: C++
Stars: 15.1k
Forks: 3.3k
Avg merge: 2d 1h
Merged PRs (30d): 83

Contributor guide

Open the contributing 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.

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
Eval bug: Ministral-3 tool-calls during reasoning are not processed Open

bug-unconfirmed

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

ggml-org/llama.cpp#29248 · Opened Sep 21, 2026
run_tests.py fails on windows, but running tests individually works Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

NVIDIA/cuda-samples#453 · Opened Sep 21, 2026

More C++ issues