From: Marcus Sundberg <mackan@stacken.kth.se>
  To  : ggi-develop@eskimo.com
  Date: Sun, 16 May 1999 19:20:52 +0000

Re: XGGI & keymaps

Andreas Beck wrote:
> 
> > I've been setting up a norwegian keymap, and now I'm more or less done.
> > There are only a few problems I've been having:
> >
> > Backspace and Delete have the same keycode... I don't like that. Neither
> > will any other Norwegian, I suspect. I don't know about you Swedes and
> > Germans :)
> 
> Hmm - that doesn't happen for me. They have different codes. 130 and 135
> to be precise.
> 
> Do you happen to have those mapped to the same symbol on your linux
> console ?

input-linux-kbd was written for the braindead, but for some reason very
common, case where Backspace is mapped to Delete and vice versa. I
remember me and Andrew having a discussion about this quite some time
ago but apparently it was forgotten about before it was fixed.

I removed Andrew's fix and changed it to use ix86 keycodes directly.
Non ix86-platforms will have to make sure that Backspace and Delete
are mapped correctly.

> > The key to the left of '1' and over 'Tab' doesn't even give xev a
> > reaction.
> 
> Confirmed. Same here.
> 
> Marcus - how does the keymapping of xggi work again ? Could you give me
> a quick reminder ? IIRC it goes incoming "label"->pseudo-keycode->
> normal X mechanisms - right ?

Yep, that's correct.

> In that case we'll have to add "^" aka 0x5e to the table, as on a german
> keyboard the key he's talking about contains ^ and that little superscript
> circle some languages use as accent or standalong as "degree" symbol.

Ok, the common case seems to be for that key to be a dead circum.
I'll add an XGGI mapping for undead circums too.

> > Can I do something about that? When I press it, nothing happens.
> > I know for a fact that the key works under XFree_SVGA. It should be
> > something like
> > keycode xxx   = bar   paragraph
> 
> That would mean we'd need "|" as well - right ?

Yes, will add that for 1.6.1.

> > PrintScreen doesn't have a keycode either (like the one above).
> 
> Same here. wait ... that one produces 0x1c for me.

Well that seems logical... Not.
Just another special case in input-linux-kbd...
Will be fixed in LibGII 0.6 too.

> > And last, the MS-keys on both sides have the same keycode. Perhaps this i
> > is normal, I don't know.
> 
> Same for me. That is probably related to the fact, that one usually doesn't
> map them in the linux console keymaps.

Well, I'm proud to say that I have eight keyboards and none of them have
Win* keys on them. ;-)
However I borrowed a keyboard with Win* keys, and it seems that they are
indeed unmapped and generate GIIK_VOID. I fixed it so that if they are
not mapped to anything else we map them to Left/Right Meta and GIIK_Menu
respectively.

> P.S.: Marcus - I attach an updated .de_de keymap that corrects two slight
> glitches. You'll probably want to include them in 1.6.1.

Yep, will do.

//Marcus
-- 
-------------------------------+------------------------------------
        Marcus Sundberg        | http://www.stacken.kth.se/~mackan/
 Royal Institute of Technology |       Phone: +46 707 295404
       Stockholm, Sweden       |   E-Mail: mackan@stacken.kth.se