On Wed, 2 Aug 2000 [EMAIL PROTECTED] wrote:

> I notice that the UK keyboard layout has some minor errors in it.  The key
> to left of the 1 key is defined as having only the character, ` back-quote
> defined.  However on all my keyboards shift this key is the 
>
>    [ Part 2: "Attached Text" ]
>
> ¬ key (a minux
> with a tail at the right) and alt-gr of that key is a solid vertical bar
> | (shift \ is a broken vertical bar ¦).  This seems to want a fix to the
> windows/x11drv/keyboard.c module, but I just wondered if there was a
> particular reason for the ommision before I proposed a patch.

How hard would it be to fix your mailer to not break up text like this? It
makes it really hard to reply to your message, since only the first part
gets quoted by my mailer, and I have to copy&paste the rest.

If the ` is correct on your keyboard, there isn't much to worry about. If
you omit anything, the keyboard code will match anything there, so you
won't lose anything. If it's incorrect, then whoever submitted that
keyboard didn't have the same layout?

> err:keyboard:X11DRV_KEYBOARD_ToAscii Please report: no char for keysym
> FE20 (ISO_Left_Tab)
> err:keyboard:X11DRV_KEYBOARD_ToAscii 
> (virtkey=9,scanCode=F,keycode=17,state=1)

I doubt this really matters. Left tabs should work anyway, I think.

> I am looked at windows/x11drv/keyboard.c, but the nearest table stops
> short of FE20.

No... all the tables apply to FFxx, there aren't any for FExx.

> Also I notice that VK_TAB is defined as being scan code 0x0F, is this
> state related and if so how does that change which table is used?

Yes, it's related because it's the same key, therefore you don't need to
add it to any tables. (The reason ToAscii gets confused is because that
routine is independent of those tables - it doesn't use them - special
keys don't generate ASCII codes anyway, so it doesn't have to.)

Reply via email to