Store instrument- and partnames in a language indendent manner

• Jun 11, 2016 - 11:23
S5 - Suggestion

When "file/parts" selected the "instruments" drop down apears in chinese like characters.

My langauage preference shows as "English (GB)"

GIT commit: 3c7a69d

Attachment Size
Musescore bug.jpg 138.88 KB


Please attach the score, I guess it has been created with Chinese settings and hence Chinese instrument names. You can check yourself, right click, staff properties. Also you can name the parts yourself, I guess the 3 are violins

Status (old) by design needs info

could I suggest a design improvement would be to store instruments as a reference number. Then they could be displayed wherever necessary according to the language of the user.
If you don't already have instrument tables in all languages then I'm sure the international Musescore fraternity would be happy to produce them...I'd certainly would be happy to do some European ones

Type Graphical (UI) Functional
Reported version 2.1  
Frequency Once
Regression No
Workaround Yes

Workaround: change the instruments under the current linguistic environment.

In reply to by Jojo-Schmitz

> As suspected: the instrument and partnames are stored in Chinese in that file, so this is by design

And the strings are obviously Japanese, not Chinese. Chinese characters are usually more complicated (than those Japanese characters which don't resemble Chinese).

But non-Asians usually can't (easily) tell one from the other, at least it is not obvious to us at all ;-)

Storing instrument names in a language independant manner would probably mean to store them in (US) English and interprete/translate them on the fly, on display.

One big challenge there: that would cause a score to look very different in the MuseScore program on the PC vs. online on! (similar issue, but of far less importance, is the display of date and time marcos in header/footer).

In reply to by Jojo-Schmitz

I would suggest we change the things stored in a musescore file to tags, or ids, not exact strings, so the software can "translate" them to the current language. And we can let the user decide if converts them to English or use the version under their linguistic environment (which is by default). Which means something like forceEnglish can be added.