Re: XKB Patch
Peter Åstrand <[email protected]>
| Newsgroups | gmane.network.rdesktop.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 15 May 2009, Ilya Konstantinov wrote: > Perhaps not for sending a suitable scancode, but one needs to tell the remote desktop which keymap to use. > > > Yes, you're referring to the "secondary keyboard language LCID" in the RDP init packet. I'm referring to the g_keylayout variable in rdesktop, which defaults to 0x409, and is otherwise set by using the "map" keyword in keymap files. It is also sent in sec_out_mcs_data, under the section: /* Client information */ out_uint16_le(s, SEC_TAG_CLI_INFO); This information tells the RDP server which keymap to use, ie how to interpret RDP scancodes. Are you sure we are talking about the same thing? "secondary keyboard" sounds strange to me. > When the XKB extension is not available, we should fall back to the > existing facility (the one which uses rdesktop keymap files). In other words: Lots of pain, no gain. If we can't get rid of the current implementation nor the keymaps, it's going to be a *lot* of work for basically no value. Rgds, --- Peter Åstrand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Linköping Phone: +46-13-21 46 00 ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ rdesktop-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rdesktop-devel