Switching language doesn't also switch instruments and palettes translation
Reported version
3.0
Priority
P1 - High
Type
Wording/Translation
Severity
S3 - Major
Status
closed
Regression
No
Workaround
No
Project
Switching language doesn't also switch instruments translation (in the add instruments dialog, of course it won't translate instruments names already in the score), but stays on the language setting that was valid on start of that MuseScore session.
Windows 7, f3a711f
Comments
Confirmed.
Offtopic, what does "i18n" tag mean? :)
internationalization, there are 18 chars between the i and the n. Compare l10n, localization, see https://en.wikipedia.org/wiki/Internationalization_and_localization
Palettes names are also not translated after switching languages. Only rerunning correctly reloads palettes and instruments.
In reply to Palettes names are also not… by Anatoly-os
Can not reproduce for palettes. Seems to be fixed for palettes now.
Switching the language again doesn't affect the translations for palettes and inspector (0128daf). Reopen palettes or inspector view doesn't work, only a restart of MuseScore.
For palettes it worked as expected with a nightly before (3543170), but not for the inspector.
3543170, is from 2013....
In reply to 3543170, is from 2013.... by Jojo-Schmitz
Really? How the time passes ;-). No, I mistyped it, second attempt: 8a42030.
Hmm, there are still quite a lot commits in between (24Oct and 1Nov)
My bet is on the workspaces PR though, https://github.com/musescore/MuseScore/pull/4079, or 9fb4549, 29Oct
It seems you're right, at least for palettes it worked with the nightly before (78fbab1), but not for the inspector.
I guess the massive changed Inspector went thru in the past years have lost the changes to update translations.
For workspaces there got to be a different reason though
Seems fixed, no idea since when, but at least in 3.2.3
In reply to Seems fixd, no idea since… by Jojo-Schmitz
But there's still suggestion about automatically updating existing instruments' translation if the linguistic environment is changed. See #114766: Store instrument- and partnames in a language indendent manner.
This issue here was about the add instruments dialog and the palettes.
Once added to a score, the translated names are 'baked in'.
Storing instrument names in a language independant manner would mean to store them in (US) English and translate them on display.
One challenge there: that would cause a score to look different in the MuseScpre program on the PC vs. online on musescore.com! (similar issue, but of far less importance, is the display of date and time marcos in header/footer)
Automatically closed -- issue fixed for 2 weeks with no activity.