Add multi-keyboard layout support

[hutiwephy]

Description of the new feature / enhancement

Add the capability of having 2 or more keyboards of different layouts connected onto the same PC and not have to switch between layouts every time I log in, wake from sleep, reboot my PC, or want to switch keyboards (ex: docking or undocking a laptop)

in short:

• Recognize the multiple keyboards
• Associate a layout to that keyboard
• And ditch the windows language bar somehow, because jumping around from layout to layout can cause problems on some apps

Scenario when this would be used?

A person that only owns a laptop, a dock solution (ex: Thunderbolt Dock, USB HUB, USB Type-C Dongle), might wish to arrive home and dock its device.
Now if that person is as lucky as I'm, they will have to deal with any task that involves the lock screen pop up reverting their keyboard's layout to the default one that is different from the laptop's keyboard layout.

To be honest Getting to the point of having the English International and Portuguese Layouts, without any other bloat layouts is a nightmare of its own involving PowerShell scripts and a LOT OF PATIENCE.

Continuing... This Feature would do some sort of dark magic to make so when I press a key with a label it matches the key label no matter the keyboard manufacturer or layout.

Supporting information

Why hasn't Microsoft fixed this yet? They promote all-in-one devices and the flexibility of tablets and laptops on their product pages, but are unable to make such a basic feature, the language bar, better.
Is it really that important to make the context menu worse on win11, and not add this something that lead to the creation of multiple projects to attempt to improve the language bar which are still not perfect.

I'm not even going to try to give this feedback to Windows team it's useless they won't fix it no matter what, this issue exists since Windows XP and some of the tools originally targeted Windows XP and Windows 7.

[crutkas]

In a perfect world, this would be done via #1460 but until we have a proper way to detect keys based on keyboard, /dup #1881 would be how we'd do this. You'd create some type of profile.

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!