One change for 0.5 is a rewrite of the keymap code. I checked in changes that
1. no more compiled in keymaps 2. genkeymap utility 3. km-xxxx.ini file changes 1. There was compiled in keymap before, they have been removed and only loaded keymaps are used. 2. The genkeymap utility builds and installs by default. Its called xrdp-genkeymap. This is pretty must a utility I got from Adam Wallner that uses XLookupString to build the kaymap file. 3. The km-xxxx.ini files now contain both the keysym and the unicode char for each key. The original design when rdp scancodes to unicode but putting the keysym in the file names since too. This way we never have to edit vnc.c when add new keymaps. To create a new keymap, get and install the latest cvs version. Set the keymap you want in local x server. run genkeymap like xrdp-genkeymap /etc/xrdp/km-0409.ini You need to have the right file name. Replace 0409 with the right number for your layout. A list can be found at http://rdesktop.svn.sourceforge.net/viewvc/rdesktop/rdesktop/trunk/doc/keymap-names.txt?revision=1487&view=markup I check in keymaps for 407, 409, 410, 419. e.g. de German (Germany), en-us English (United States), it Italian (Italy), and Russian. If this method works for everyone, I can start checking in more keymaps. If you have had keymap issues, give this a try to see if the issues are resolved. Thanks, Jay ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
