From: <sch...@mu...> - 2002-10-12 19:06:11
|
Hi Peter Below you see the danish keymap. I havn't included the keys that works correctly (0 - 9, a - z, A - Z). I havn't included the Windows keys either cuz' I didn't knew what to call them cuz' they were all detected as 'NoSymbol'. Regards Søren Schimkat ---------------------------------------------------------- # Danish include common map 0x406 onehalf 0x29 section 0x29 shift threequarters 0x29 altgr exclam 0x2 shift exclamdown 0x2 altgr quotedbl 0x3 shift at 0x3 altgr numbersign 0x4 shift sterling 0x4 altgr currency 0x5 shift dollar 0x5 altgr percent 0x6 shift ampersand 0x7 shift yen 0x7 altgr slash 0x8 shift braceleft 0x8 altgr parenleft 0x9 shift bracketleft 0x9 altgr parenright 0xa shift bracketright 0xa altgr equal 0xb shift braceright 0xb altgr plus 0xc plusminus 0xc altgr question 0xc shift dead_acute 0xd dead_grave 0xd shift bar 0xd altgr lstroke 0x11 altgr EuroSign 0x12 altgr registered 0x13 altgr thorn 0x14 altgr leftarrow 0x15 altgr downarrow 0x16 altgr rightarrow 0x17 altgr oe 0x18 altgr aring 0x1a Aring 0x1a shift dead_diaeresis 0x1b dead_circumflex 0x1b shift dead_tilde 0x1b altgr ordfeminine 0x1e altgr ssharp 0x1f altgr eth 0x20 altgr dstroke 0x21 altgr eng 0x22 altgr hstroke 0x23 altgr kra 0x25 altgr lstroke 0x26 altgr ae 0x27 AE 0x27 shift oslash 0x28 Ooblique 0x28 shift apostrophe 0x2b asterisk 0x2b shift dead_doubleacute 0x2b altgr less 0x56 greater 0x56 shift backslash 0c56 altgr guillemotleft 0x2c altgr guillemotright 0x2d altgr copyright 0x2e altgr leftdoublequotemark 0x2f altgr rightdoublequotemark 0x30 altgr mu 0x32 altgr comma 0x33 semicolon 0x33 shift dead_cedilla 0x33 altgr period 0x34 colon 0x34 shift periodcentered 0x34 altgr minus 0x35 underscore 0x35 shift hyphen 0x35 altgr ---------------------------------------------------------- Peter Åstrand wrote: >>I would be happy to supply the danish keymap - but I'm not quite sure >>how to read the scancodes. >> >> > >For all keys that gives warning messages about "No translation", do: > > 1. Get the "key number" for this key, by looking at > http://www.cendio.se/~peter/rdesktop/keynums.png . > > 2. Take a look at scancodes.h, and look for > SCANCODE_KEY_<my-key-number>. The scancode value is at the end of > the line. If the line contains (SCANCODE_EXTENDED | 0xsomething), > then you should OR 0x80 to this value. For example, you can do: > > python -c "print hex(0x80 | 0xsomething)" > > 3. Put the scancode (from step 2) and keysym name (found in the > error message) into the keymap file ("da" in your case). > > >/Peter > > > >>Peter Åstrand wrote: >> >> >>>Søren Schimkat wrote: >>> >>> >>> >>>>I've just compiled the CVS verions of rdestop - and it seems to work >>>>just fine. But there is an errormessage saying: >>>> >>>>ERROR: No translation for (keysum 0x21, [different chars]) >>>> >>>>What does it mean? I have thougt of just removing the errormessage >>>>form the source - but i guess that it means something.... >>>> >>>> >>>It means that the keyboard map you are using does not contain a >>>translation for this key. It could be either because you are pressing a >>>really strange key like "Stop" on a Sun keyboard (which does not make >>>sense in Windows), or (more likely) that the keymap you are using is not >>>finished. >>> >>>Currently, the CVS version only contains full keymaps for English, >>>Swedish, Finnish and possibly some other countries. If anyone has other >>>keyboards and want to help with finishing the keymaps, this would be >>>very appreciated. It's not very hard if you have the right keyboard. >>> >>>Also, note that currently you must use the correct case. So, "-k DK" >>>probably won't find any keymap, but "-k dk" will. >>> >>>/Peter Astrand, >>>rdesktop team >>> >>> >>> >>> >> >> >> > > > |