Looking to confirm I’m not mad:
While literally 100% of programs I know care about “key strokes” when triggering keyboard shortcuts, Dorico cares about… um… characters?
For instance, in my multi-language keyboard on every program Ctrl+A selects all. Duh. But here’s the nuance, It’s not really Ctrl+A. It’s the Ctrl key, plus the A key, which means it works even when I set the language on the keyboard to… say… Hebrew. (See attached image).
So on my keyboard: When in English mode, Ctrl+A is select all, and when in Hebrew mode, Ctrl + ש is select all, which is no surprising, because it’s THE SAME KEYS (see image again).
This is not the case in Dorico, and Dorico seems to be the ONLY program I know that behaves this way. If I switch my keyboard from English to Hebrew, all of the keyboard shortcuts stop working, because Dorico ignores the actual key stroke combination, and in actuality only recognizes triggered characters.
This is causing a lot of “WTF” moments in my workflow when all of a sudden all of my keyboard shortcuts stop working and it takes me a second to realize “oh, I need to switch back to English”, because I set my shortcuts on the English mode".
Any thoughts why this idiosyncratic behavior (that like I said seems to only exist in Dorico) was selected?