The other RDC software have long understood that character translations (not key mapping) is the easier solution MS RDC couldn't be dumber than that if it wanted to. If I press shift+2 on macOS side, I will get various characters on the windows side, depending on what keyboard layout is chosen in windows language settings. If I press a key, windows just get that key stroke and will print whatever character this key means in the installed keyboard layout on the windows side. I concluded that the reason is because Microsoft RDC must still use the last-century physical key mapping technique. (|"\etc that I type on my Dutch macOS keyboard are correctly sent to windows 10.Īfter numerous testing, discussion with keyboard experts, other RDC software etc. Once I'm connected, none of the special characters, e.g. I installed Remote Desktop client for MacOS to connect to a remote windows 10 computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |