Changing a default voice for (base)drum entry changes shortcut from A to L, which is then unusable

• Nov 12, 2015 - 06:57
Type
Wording/Translation
Severity
S4 - Minor
Status
closed
Project
MuseScore

I notate the snare drum always in voice 2.

So I want to change the default voice for Acoustic Snare in "Edit Drumset" to Voice 1.
When I do that, the shortcut in the Cell Palette becomes L and unusuble.

Attachment Size
L.png 5.6 KB

Comments

• Nov 12, 2015 - 12:21

I am on MuseScore 2.0.2,
Windows 7 TR (Ultimate, 64bit) and,
Ubuntu 14.04.3 LTS.

In both changing voice from 1 to 2, causes it to turn L.

Reply

• Nov 12, 2015 - 12:21

I am on MuseScore 2.0.2,
Windows 7 TR (Ultimate, 64bit) and,
Ubuntu 14.04.3 LTS.

In both changing voice from 1 to 2, causes it to turn L.

Reply

• Nov 12, 2015 - 16:30

Ok. The one that you've sent is OK.

But when I try to change it back to voice 1, it again turns L.

Now... I see that it now writes "Akustische Snare" on the cell...

Maybe the bug is about localization or something!?

Reply

• Nov 12, 2015 - 17:40

Ah, yes, well possible, ISTR that these string, including the shortcuts, are translatable.
And I'm using a German Translation, whch are you using?
Does A still work as a shortcut, regardless or it being listed as L?

Reply

• Nov 13, 2015 - 07:08

Hmm. When I think about it, yes the issue can really be about localization.

I am using MuseScore in Turkish. In Turkish, notes are never named as "A, B, C, D..."
They are used as "La, Si, Do, Re..."

In regard, maybe the translator, translated the shortcut 'A' as 'L' (which is short for La).

But in practice, L doesn't seem to be a valid shortcut for the MuseScore code. It DOES NOT WORK.
'A' key does not work either (when it is 'L').

Shortcuts should not be translated. They should be left as they are.

Reply

• Nov 13, 2015 - 08:14

Yes, These shortcuts should not get translated, that much is a bug and one I've noticed quite a while ago.
Should be easy so Workaround, by fixing the turkish translation, I'll see what I can do there.

I believe it is then strings 102-108, I've now removed them from the Turkish translation, try updating translations to see whether it works now.

And I think I found the offending code...

Reply

• Nov 13, 2015 - 09:14

See https://musescore.org/en/handbook/language-settings-and-translation-upd…

looking at other translations:
Asturian translatates "A" as "A (la)", which seems to not have a bad effect. Seems a clever approach?
Catalan, Catalan (Valencia), Galizian, Italian, Portuguese (Brazil), Spanish use the same bogus translations as Turkish (used to use), so same workaround is needed.
Georgian, Hindi, Ukrainian too, but with different character sets. Not sure whether the workaround works there, whether the corresponding keyboards do have the letters A-G
Czech, Danish, Hungarian, Norwegian (Bokmal), Polish, Serbian, Slovak, Slovenian translate B with H, which aint't gonna work.

Reply

• Nov 13, 2015 - 09:32
Title Changing a default voice to A, makes it L (unsuable) in the palette. ⇒ Changing a default voice for (base)drum entry changes shortcut from A to L, which is then unusable

Reply

• Nov 13, 2015 - 10:35

Thanks for confirming that the Workaround does the trick.
Let's see whether I'll use that for the other affected languages too...

Is still not 100% OK though, if you change the shortcuts for (general' note entry, e.g. from B to H (like I'd like to do as that's the proper notename here in Germany), the drum entry palette still shows B, but wants an H being used. Probably also the reason why we can't add more shortcuts, like H, J, K, similar to 'add fret to string' in tablatur.

Reply

• Nov 13, 2015 - 10:58

Applied the workaround to the translations for Catalan, Galizian, Italian, Portuguese (Brazil), Spanish, can't do it for Catalan (Valencia) though, due to these strings having been reviewed.
Not sure I should tamper with Georgian, Hindi, Ukrainian, and for Czech, Danish, Hungarian, Norwegian (Bokmal), Polish, Serbian, Slovak, Slovenian it may even work id the note entry shortcut is setup properly?

Reply