[SunRay-Users] force Windows to use US-international keyboard instead of locale keyboard?
the.loeki at gmail.com
Tue Mar 23 20:11:02 EET 2010
The hotfix that supplies the functionality is very outdated ;-)
But the functionality has been in Windows since then, and the described
workaround works as well.
It would seem Windows is capable of detecting a difference between locale
and keyboard, which doesn't immediately exist in what the RDP clients
I've for example also tried to use -l nl-NL -k en-US but that doesn't work
Besides, there's no immediate keyboard/locale definition for what Microsoft
calls "US International"
We've now implemented group policies forcing the keyboard correctly and the
IgnoreRemoteKeyboardLayout setting and we left it at that ;-)
On 23 March 2010 09:27, Ivar Janmaat <ijanmaat at xs4all.nl> wrote:
> This appears to be the case for rdp clients like uttsc, rdesktop and
> However the Microsoft rdp client on a Windows system does not seem to have
> this problem.
> A Windows rdp client can connect with Language-Dutch ande
> Is Microsoft using some undisclosed rdp features to do this?
> Thanks for the link.
> I found this also but thought is was a bit out dated.
> The Loeki schreef:
> There appears to be no correct setting for Language-Dutch,
>> I always use this:
>> It's a registry setting that's aptly called IgnoreRemoteKeyboardLayout. It
>> allows you to define your own settings within Windows, completely ignoring
>> what the RDP client says.
>> You can of course forget about the compose key doing anything functional
>> in Windows. Windows doesn't know what to do with it. So with
>> US-International you will get the Windows-deadkeys feature, i.e. press quote
>> and then the e to get é and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SunRay-Users