I also just added the --kbd-list option which prints out all known keyboard
ids. of course, if you have a custom keyboard layout, it's not in the "known
list". this list is there for reference
On Thu, Aug 25, 2011 at 9:37 PM, Marc-André Moreau <
marcandre.mor...@gmail.com> wrote:
> I have just re-introduced the -k option
>
> For the keyboard layout to be accepted, you need to log out and log back in
> (the remote session)
>
> For a quick test, use -k 0x408, it's a greek keyboard layout so it'll be
> quite obvious if it worked or not.
>
> On Thu, Aug 25, 2011 at 9:18 PM, Marc-André Moreau <
> marcandre.mor...@gmail.com> wrote:
>
>>
>>
>> On Thu, Aug 25, 2011 at 8:44 PM, <free...@martins.cc> wrote:
>>
>>>
>>> > FreeRDP could have a 'use client side keyboard layout'
>>> > mode that worked that way. But since you are moving
>>> > modifier keys around I doubt it will help you.)
>>>
>>> I just make the caps control key be an extra control key.
>>> Again, it works on the linux X system via xmodmap, it works
>>> on the windows console via a register keyboard layout entry,
>>> it works when I rdesktop from linux to windows, so it is
>>> possible and I've been working like this for several years.
>>> I was just giving FreeRDP a try as I think it's going to be
>>> a better program.
>>>
>>> > The basic mode of operation for the RDP protocol is to
>>> > transfer some kind of keyboard scan codes to the server
>>> > and the server uses its keyboard layouts to map to unicode
>>> > symbols and modifiers.
>>>
>>> When I press the left control key xev shows me a keycode of
>>> 37 and a keysym of 0xffe3. When I press the caps control
>>> key xev shows me a keycode of 66 and the same keysym. My
>>> local applications probably only get the keysym. I guess
>>> FreeRDP is sending the different keycodes to the remote
>>> system and rdesktop some keycode equivalent to the keysym.
>>>
>>> > I guess your problem is that xfreerdp happens to give a
>>> > keyboard layout hint to the server that do that it doesn't
>>> > use your custom layout on the server side.
>>>
>>> On the remote side I have a scancode map in the register:
>>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout]
>>> which only maps capslock to left control. On the console
>>> keycodes get mapped through it. With rdesktop the remote
>>> system never gets a caps lock keycode, with Free RDP it
>>> does. I wonder if there is a way to tell the terminal
>>> server to map through it. That would solve my problem.
>>>
>>
>> That's perfect, do you have the ID? For instance Canadian Multilingual
>> Standard is 0x00011009
>>
>> I just checked and the keyboard layout options aren't in 1.0 yet, but once
>> they'll be back in all you'll need to do is add -k <keyboard layout id> to
>> your command line
>>
>>>
>>> -- Henrique
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> EMC VNX: the world's simplest storage, starting under $10K
>>> The only unified storage solution that offers unified management
>>> Up to 160% more powerful than alternatives and 25% more efficient.
>>> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
>>> _______________________________________________
>>> Freerdp-devel mailing list
>>> Freerdp-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freerdp-devel
>>>
>>
>>
>
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Freerdp-devel mailing list
Freerdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
