Keyboard layout missing apostrophes

Hello

That's strange and annoying indeed, I'm sorry for the inconvenience, but I can't explain it off hand with a code change on our side nor can I reproduce it.

What keyboard layout do you use on your Mac?

What do you have configured for keyboard layout and "send input as unicode"? That's in the RDP session settings, under Local Resources > Keyboard. If you have "Default", the defaults are in the application settings, under Types > Remote Desktop (RDP) > Keyboard. If layout is at "default", it means "use the keyboard layout I have configured on my machine (see my first question above).

Thanks and kind regards,

Everything is on Default inside RDM. Since day one (over 2 years ago), I configured my US English keyboard as "US English - International" and it has been working fine till now. On the remote RDP sessions, some have the default US English and some have the "US English - International" keyboard layout. the failure comes on all RDP sessions.
"send input as unicode" is on Default on RDP sessions and YES on the RDM main RDP type settings.

I just switched that last one to NO, saved, and restarted RDM and now the quotes are working fine.

Thank you very much for the clue !!! 👍

Hello

Scancode input can be a good workaround in this case indeed. However; I'm a little bit surprised; on a US - International keyboard layout, single and double quotes are dead keys and used to combine with other letters to create accents. So, for example, you press ' and then the system waits for a second letter to combine it with (on my Mac, in a regular text editor, the ' is highlighted yellow to show this). Then you press "Space" to output the quote, or something like "e" would produce é.

Is that what you're used to? Because, if that's the case, and this was working for you before, it would indicate something has broken with dead key handling on the RDM side. But it's also interesting I didn't hear any other reports of this.

Regardless, if you don't want to pull on it further, scan code input can work.

When you choose to send scan codes, the key presses are sent as (for example) "the third key from the left on the middle row" and then the server simply simulates that physical key press. You can understand that in that case, it's important for the local and remote keyboard layouts to match otherwise it causes confusion. In unicode input, the same key press would be sent as the character "d" (on my keyboard) and the server simply injects that character directly. Unicode sidesteps a lot of issues with keyboard mapping, but it puts extra work on the client (especially with things like dead key handling).

Please let me know if something isn't clear or you have other questions

Kind regards,