RE: [rdesktop-devel] Keymaps

[Casey A. S. <cs...@se...>]

Seems I just wasted a lot of time writing the dv layout which I don't =
need
at all...

I was using the dv.orig file with Xnest, because I couldn't find a way =
to
make Xnest use a non-qwerty layout.

When I stopped using Xnest, my rdesktop -k dv started not working, so I
spent quite some time making the dv file (which took a long time =
because
there seems to be no relationship between the codes that the rdesktop
layouts use and what xev outputs, so it was mostly guesswork).  Ah =
well,
live and learn.

- Casey

> -----Original Message-----
> From: Matt Chapman [mailto:mat...@cs...]
> Sent: 12. ma=ED 2003 08:11
> To: Casey Allen Shobe
> Cc: rde...@li...
> Subject: Re: [rdesktop-devel] Keymaps
>=20
>=20
> No idea, what's are the symptoms when you use the standard=20
> en-us keymap
> (i.e. 0x409 on the Windows side) with a Dvorak X11 layout?
>=20
> Matt
>=20
>=20
> On Mon, May 12, 2003 at 04:02:04AM -0400, Casey Allen Shobe wrote:
> > Well, the dv keymap I made worked under X11/qwerty, but not=20
> X11/dvorak (both
> > PC).  Thus, I had to write another (see previous posting=20
> for keymap files
> > and explanation).
> >=20
> > Care to explain?
> >=20
> > - Casey
> >=20
> > > -----Original Message-----
> > > From: Matt Chapman [mailto:mat...@cs...]
> > > Sent: 12. ma? 2003 07:57
> > > To: Casey Allen Shobe
> > > Cc: rde...@li...
> > > Subject: Re: [rdesktop-devel] Keymaps
> > >=20
> > >=20
> > > On Mon, May 12, 2003 at 03:42:15AM -0400, Casey Allen Shobe =
wrote:
> > > > Hmm, well that makes sense.
> > > >=20
> > > > So from what I understand, this is what happens:
> > > > * Physical keyboard sends signals to the physical terminal.
> > > > * The operating system translates these into scancodes or=20
> > > maybe the keyboard
> > > > just sends them directly.
> > > > * xkb translates scancodes into keysyms (whatever those are).
> > >=20
> > > Keysyms are a machine/keyboard independent representation.
> > >=20
> > > > * rdesktop client translates keysyms into PC scancodes.
> > > > * Windows recieves PC scancodes which override any Windows=20
> > > keyboard layout
> > > > setting.
> > >=20
> > > rdesktop can specify what keyboard layout ID it wants out=20
> of the ones
> > > installed on the Windows server.
> > >=20
> > > > Instead, you have to write an rdesktop layout for any=20
> > > keyboard layout and
> > > > any possible xkb layout (in my case, pcqwerty-->pcdvorak and
> > > > pcdvorak-->pcdvorak).  But when I want to run rdesktop on=20
> > > linux/sparc, I
> > > > suppose I'll then need to write an rdesktop layout for=20
> > > sundvorak-->pcdvorak,
> > > > or if I should happen to want to use it within X11/qwerty=20
> > > on linux/sparc,
> > > > I'll then need to write a sunqwerty-->pcdvorak, or if=20
> > > there's a qwerty Sun
> > > > user, then I'll additionally need to write a=20
> sunqwerty-->pcqwerty?
> > >=20
> > > Nope, you only need to write a keymap for each distinct=20
> > > keyboard layout,
> > > that is a keyboard layout which is not a subset of=20
> another keyboard
> > > layout (the position of the keys and the X server being=20
> irrelevant).
> > >=20
> > > IMHO there's no need for a Dvorak layout since there's no new=20
> > > keys on a
> > > Dvorak keyboard - you can use Dvorak on the X11 side and=20
> QWERTY on the
> > > Windows side, and the user can't tell the difference.
> > >=20
> > > Matt
> > >=20
>=20