Remote Desktop for macOS still failing to correctly handle language detection...

%3CLINGO-SUB%20id%3D%22lingo-sub-2995809%22%20slang%3D%22en-US%22%3ERemote%20Desktop%20for%20macOS%20still%20failing%20to%20correctly%20handle%20language%20detection...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2995809%22%20slang%3D%22en-US%22%3E%3CP%3EWindows%2011%20is%20now%20upon%20us%20and%20I%20am%20now%20testing%20it%20for%20some%20of%20my%20forever%20Microsoft%20bugbear%20failures%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBugbear%201%20-%20Remote%20Desktop%20Language%20Handling%20-%20FAIL%3C%2FP%3E%3CP%3ESCENARIO%3A%20Using%20Remote%20Desktop%20for%20macOS%20to%20connect%20from%20a%20Mac%2C%20with%20Language%20%26amp%3B%20Region%20settings%20set%20to%20English%20(Australia)%20-%20English%20(US)%20is%20not%20even%20installed%2C%20the%20target%20Windows%20system%2C%20now%20running%20Windows%2011%20also%20with%20Language%20settings%20all%20set%20to%20%22English%20(Australia)%20-%20English%20(US)%20also%20removed%2C%20all%20English%20(Australia)%20language%20pack%20components%20downloaded%2C%20installed%20and%20updated.%20All%20Admin%20templates%20and%20system%20local%20set%20to%20%22English%20(Australia)%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERESULT%20-%20FAILURE%3A%20When%20connecting%20as%20above%2C%20the%20session%20sets%20the%20default%20language%20to%20%22English%20(United%20States)%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETHEORY%20OF%20WHY%20THIS%20STILL%20FAILS%2C%20AFTER%20DECADES%20OF%20THIS%20FAILING%3A%20Microsoft%20are%20still%20using%20the%20keyboard%20layout%20to%20define%20the%20language%20for%20the%20remote%20session.%20As%20Australia%20uses%20the%20same%20keyboard%20layout%20as%20the%20US%2C%20the%20session%20is%20incorrectly%20set%20to%20%22English%20(United%20States)%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESUGGESTED%20RESOLUTION%3A%20Use%20the%20language%20settings%20of%20the%20local%20system%20and%20not%20the%20keyboard%20layout%20to%20work%20out%20what%20language%20to%20use!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECOMMENT%3A%20Sheesh!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Windows 11 is now upon us and I am now testing it for some of my forever Microsoft bugbear failures:

 

Bugbear 1 - Remote Desktop Language Handling - FAIL

SCENARIO: Using Remote Desktop for macOS to connect from a Mac, with Language & Region settings set to English (Australia) - English (US) is not even installed. The target Windows system, now running Windows 11, also with Language settings all set to "English (Australia)" - English (US) also removed and all English (Australia) language pack components downloaded, installed and updated. All Admin templates and system local set to "English (Australia)".

 

RESULT - FAILURE: When connecting as above, the session sets the default language to "English (United States)".

 

THEORY OF WHY THIS STILL FAILS, AFTER DECADES OF FAILURE: Microsoft are still using the keyboard layout to define the language for the remote session. As Australia uses the same keyboard layout as the US, the session is incorrectly set to "English (United States)".

 

SUGGESTED RESOLUTION: Use the language settings of the local system and not the keyboard layout to work out what language to use!

 

COMMENT: Sheesh!

0 Replies