musescore / musescore/MuseScore

Properties panel doesn't have any translations (5.0 main)

Open
#33,976 0 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Jun 26, 2026.

P1 regression nightly 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

See https://github.com/musescore/MuseScore/pull/33514#issuecomment-4530687796 for explanation:

This means the affected strings will appear untranslated (i.e. always English) in builds of the main branch until we switch Transifex from 4.7 to main, which we will probably do a few weeks prior to a 5.0 alpha or beta release.

(We won't switch earlier because translators are still translating 4.7 strings, which enables users to receive language updates via Preferences in 4.7.)

When we switch, Transifex will recognize that the "propertiespanel" strings are identical to the old "inspector" strings. It will copy the translations automatically from its Translation Memory, so no translations will be lost.

5.0 main nightly

Image
Supporting files, videos and screenshots

1

In which versions of MuseScore Studio is this issue present?

5.0.0-260626043

Regression

Yes, this works in the latest released version and is broken in the nightly builds

Operating system

Windows 10

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

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.