Unrecognized Keyboard Layout After Login

Unrecognized keyboard layout after login

This could be a keyboard priority issue. On Unity dash, search for "System settings" then open: System settings > Text Entry. Then use the ^ arrows to move up the layout you want to be the default keyboard layout. Make sure that your preferred keyboard layout is number one on that list. I would also suggest that you also remove all keyboards layout(s) you do not need/use, use the - and - buttons to add or remove keyboard layouts respectively.Then next time you restart you systems the changes should take effect

------

German characters on US-International keyboard layout

Press Shift " keys. Nothing should appear on screen. Now press A and you get . Similarly for and .Note: Press space if you wanted " (double quotes). So you need to press Shift " and then space to get a single double quote in International US keyboard.

------

How do I use a custom keyboard layout created with Microsoft Keyboard Layout Creator in Windows 8?

Yes, there is a way to use the MSKLC custom layout in Windows 8.1. It's not more than a workaround, I would say, but it works:Go to Control Panel Language Advanced SettingsUnder Switching input methods select Options and then Advanced Key SettingsHere you can assign a shortcut that directly activates your custom keyboard layout (in combination with a language, so if you want to use the same layout with different languages, you need one shortcut for each combination in order to swap between these).BTW: I suspect that the reason, why some people report that MSKLC works with Windows 8 is that they have only one keyboard layout or one language installed so that the system automatically uses the custom layout and hence there is no need for all of the above.

------

What is the 'international english' keyboard layout for localectl

That depends on what you consider international, let's go through a common output of localeclt and see how the keyboards differ:OK, for a start we can drop out the ones that have cz, since it is for Czech keyboards. Originally Czech typewriters used QWERTZ as the top row, this is the same as in most German dominated countries (part of Germany or of Austro-Hungary). In these places keyboards start with the QWERTZ row. is and br are for Iceland and Brazil, both places have more than one official keyboard layout: One following US convention latin1 and another adding language specific letters.We have:amiga was used by the Amiga computers, a keyboard that had the arrows in a cross. atari is another keyboard that is machine specific (atari machines). acentos was a layout that tried to add latin1 letters for other languages into the US layout. It failed to do so because of ISO8859 (which divided parts of the letters that were meant to be composed there).mac is the layout specific to Mac machines in which the command key plays a very important role. sunt are musical keyboards with several programmable keys.dvorak is a layout that is argued (for some 20 years) to allow for faster typing speed. The layout is very different from any other keyboard layout. We still have:Because of the use of ASCII as the base of communications between computers the us keyboard is the base for keyboard layouts. The uk keyboard is based on the us keyboards. whilst the " is above the 2 and the pound sign above the 3. Therefore your best choice is us, since it is the original layout from which almost all others are derived.I am writing this from an Arch Linux which I installed by loading the keys as:The map file for the layout is at:(inside X11 you use Xorg's maps with setxkbmap us)

------

Custom language for Microsoft Keyboard Layout Creator (MSKLC)

I do not have any real solution, the workaround - is to create a keyboard-map and categorise it as a language which is not likely to be used side-by-side with your target language (in your case Khasi).I will share my experience, let's try to solve this together.I know that some [SIL] issued windows keyboard maps - chose this same solution - for example the SIL-IPA map - categorised itself as "Icelandic" (mentioned in some readme "(I) - to match IPA" as a mnemonic).I've recently made keyboard maps for the Fur language by request (iso 639-3: fvr) - and I chose to categorise it as a "Mori" keyboard, as I was looking for the language least possible for a user to need to co-type with Fur.(Fur keyboard maps example)The obvious minuses of that are:I've corresponded with a group working on Masalit language (Iso-639 mls/mdg) - they did the same solution with "Turkish" as their mapping.(Masalit keyboard examples)I've tried various fiddlings with "MSKLC" - and I've figured out that if you use any non-listed language code that MSKLC does not know - it will compile the output keyboard installer with the default language installed on your system, which is really not what we want.What I have tried:That's all I know for now, I will be happy to hear of real solutions, or post one if I get there!Note -- I've just found this link - which seems to be doing something like that - I cannot add the link as I do not have the are putation' here to do so: the title is "MSKLC keyboard layout names in your own language by Michael S. Kaplan," - it seems to be not simple, once anyone can get it working - it could be cool to make a small script(?) or tool to wrap it.there's also a discussion on 'cpan' that note that "(the last 4 digits match the codepage in the .klc file)" - I will try that soon.