-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate the "The Microsoft Keyboard Layout Creator" into Powertoys #5859
Comments
That link seems to be broken |
ok - looks like Microsoft have decommisioned the page. KBD Halmak "Halmak - AI designed keyboard layout" COPYRIGHT "Copyright (C) 2016 Nikolay Nemshilov" COMPANY "Halmak" LOCALENAME "en-US" LOCALEID "00000409" VERSION 1.0 SHIFTSTATE 0 //Column 4 LAYOUT ;an extra '@' at the end is a dead key //SC VK_ Cap 0 1 2 02 1 0 1 0021 -1 // DIGIT ONE, EXCLAMATION MARK, KEYNAME 01 Esc KEYNAME_EXT 1c "Num Enter" DESCRIPTIONS 0409 Halmak - AI designed keyboard layout LANGUAGENAMES 0409 English (United States) ENDKBD |
Actually MS have re-released the application at this new webpage: https://www.microsoft.com/en-us/download/details.aspx?id=102134 |
I change this to a keyboard manager issue |
If the open source problems were overcome, could the full keyboard layout creator be added to the keyboard manager section? |
@ajhawkings So the thing is I think Microsoft will not publish the code of the keyboard layout creator. So we would need to write a new one. And when they would publish it, we need someone who wants to add it to PowerToys. That's a lot of work and we aren't that many people. |
MSKLC does not support compiling the layout to ARM64. This feature would be very much needed! |
In fact the least effort is to allow Powertoys to map any character to any key. If you can allow Powertoys to map any character to any key, then the problem will be solved. |
Yes you can. Just use shift. |
No I can't because I'll be using < shift ; > for another character, and < shift : > for yet another character..... |
Something I can't find a solution for right now in Keyboard Manager is mapping a key to a dead key. For example, in US International layout, I would like to have some more dead keys so I can print caron and macron accents, as used in Maori, Pinyin and several Slavic languages. Adding more dead keys is solvable by creating a custom keyboard in Microsoft Keyboard Layout Creator, but that has its own annoyances in that for some reason loading a custom US International keyboard into an existing region seems to also end up creating an additional "ghost" non-international US keyboard for the region, which makes Win+Space region switching less intuitive than it should be. Keyboard Manager works great for doing single key replacements, though, so it would be cool if it also supported standard dead keys, as also discussed in #10082. For now I am trying to use the new Quick Accent tool, but it is a bit confusing to have one way to type accents that we used for decades (dead key), and now there is a different way to type accents that feels slower because of the requirement to long press certain letters as if it was a touchscreen. |
Actually there are more ways: Dead keys, Alt-codes, Emoji input panel... |
Key mappings are not layouts... |
Key mappings are definately not keyboard layouts, it's an important point! The ask: |
I used MSKLC to create my own keyboard layout and have used it for many years.
And completely agree with @c4tch that "Key mappings are definately not keyboard layouts." |
It's 2025 and I cannot change my keyboard layout as I wish in windows 11. Please implement this. |
📝 Integrate the "The Microsoft Keyboard Layout Creator" into Powertoys
The Microsoft Keyboard Layout Creator (MSKLC) extends the international functionality of Windows 2000, Windows XP and Windows Server 2003 systems
_Would be nice to get this Microsoft application integrated into Powertoys, so it's supported in Windows 10.
https://support.microsoft.com/en-ph/help/823010/the-microsoft-keyboard-layout-creator
The text was updated successfully, but these errors were encountered: