Kuth wrote:...I was under the same assumption you were Fish, that a US keyboard would use UK settings as...
Uh, I don't think I was under that impression at all. I have 3 set ups for my US keyboard;
US english, because it's an american keyboard.
UK english, so I can type in £ signs if I ever need to, or get at ¬ and ¦...
And US Dvorak, because Dvorak is a nightmare.
Before I set up these additional layouts, just having US english (because I have a US keyboard on this computer, and back when this was posted, I was using a laptop with a UK keyboard), multiwinia has since used en_US.txt, which is why I even have it. When starting it up now, I would have expected Multiwinia to detect which keyboard profile was in use at start up and use that keyboards locale file, but probably never check again. It apparently doesn't do this, and in my scenario, it currently seems to be using en_UK.txt even when it probably shouldn't be.
Basically US and UK keyboards are different in that UK keyboards have 1 extra key (due to a less wide left shift) and a different shaped return key. Beyond that, at least nowerdays, it's just the way the computer interprets the input from the keyboard; my US keyboard in UK layout can quite happily give ú and ó and í etc.
Kuth wrote:Though does this mean the teamspeak is still disabled? Are the only the commands that are changed and the keys re-bound the ones that don't work in their default settings?
As an aside, what's this about, I don't really understand what you mean.