bkunda

> Seems easy enough! Happy to do it :) Thank you so much 🙏🏻

Re-tested on MacOS and the unevenness is no longer so discernible. I think this is pretty much fixed! (FWIW, I did still detect some slight unevenness with the flute playback,...

@quinnouyang this is coming along well! Only one issue I found: - On Mac, when using a QWERTZ keyboard (German), I am unable to trigger the "natural" command. In this...

> I think the issue is on how we encode "secondary" characters on certain keyboards Sounds like this might need some further investigation then. @cbjeukendrup @RomanPudashkin @Eism if you have...

@Eism I'm going to suggest we implement this and then raise the issue described above (about the Shift key not working on some – i.e. QWERTZ – keyboards) as a...

Thanks for the concise summary @MarcSabatella. That all sounds exactly what I was expecting from this PR. I did mention above that I think this is ready to be merged,...

> > I notice that we encoded some characters using their [references](https://dev.w3.org/html5/html-author/charref), e.g. < is > @quinnouyang Yes, we should not use such characters in the shortcut file. And I...

@Eism I'm afraid the change from using `+` to `Shift`+`=` has worsened the user experience of this fix: - The regular `+` key on a numpad now no longer toggles...

> @bkunda Does '+' work for you on macOS? > > > The regular + key on a numpad now no longer toggles the sharp accidental. This affects all users...

> fwiw, You might be using the wrong names? Isn't `Shift + =` the same as `+`. When you say `+`, you might be meaning just `=` :) No when...