Scott Dustin Penrose's Homepage

QUEST

A search for an alternative that meets cognitive criteria

1 The Honeywell Internet Keyboard

2 Basic Mapping Codes for X11 v4

2.1 Here is the entry in /etc/X11/xkb/symbol/

2.2 What else do you have to change.

2.2.1 rules/xfree86

2.2.2 rules/xfree86.lst

3 KDE

4 Page History

1 The Honeywell Internet Keyboard

I have no idea if this is the correct name, on the bottom of the keyboard it says:

• Honewell
• Model No: Euroboard
• Part No: 123733-001
• Designed for some type of windows intel os.

2 Basic Mapping Codes for X11 v4

The entries are in HEX in the standard key <Ixx> format in xkb entries.

2.1 Here is the entry in /etc/X11/xkb/symbol/

Note that I did not bother separating the files, which I will may do if I can't get the server actually patched.

I have the separate file here which you should stick in /etc/X11/xkb/symbol/ and then change the entries in rules.

NOTE: The entries in the symbols/honeywell file are the correct standard X11 Format, where as here I have used F13+, see KDE below.

partial alphanumeric_keys 
xkb_symbols "honeywell" {

    // Describes the extra keys on a Honeywell "Internet" keyboard.

    name[Group1]= "Honeywell";
    // Game
    key <I10>   {       [ F16                   ]       };
    // Rewind
    key <I12>   {       [ F20                   ]       };
    // Eject
    key <I17>   {       [ F25                   ]       };
    // SC 2
    key <I18>   {       [ F19                   ]       };
    // Play
    key <I19>   {       [ F22                   ]       };
    // SC 1 
    key <I1E>   {       [ F18                   ]       };
    // Mute
    key <I20>   {       [ F27                   ]       };
    // Fast Forward
    key <I22>   {       [ F21                   ]       };
    // Stop
    key <I23>   {       [ F23                   ]       };
    // Mail
    key <I24>   {       [ F14                   ]       };
    // Screen Saver
    key <I25>   {       [ F13                   ]       };
    // Calculator
    key <I26>   {       [ F17                   ]       };
    // Volume -
    key <I2E>   {       [ F26                   ]       };
    // Volume +
    key <I30>   {       [ F24                   ]       };
    // WWW
    key <I32>   {       [ F15                   ]       };
    
};

2.2 What else do you have to change.

2.2.1 rules/xfree86

Add the other mappings that are already used, eg:

honeywell = xfree86 pc(pc104)

honeywell us = us(pc104)+inet(honeywell)

If you want to have a separate file (eg: symbol/honeywell) then you would probably need to use...

honeywell us = us(pc104)+honeywell(honeywell)

etc.

Copy another entry as an example

2.2.2 rules/xfree86.lst

This allows programs to find the entry...

honeywell Honeywell Internet

3 KDE

The problem with KDE 2.x is that it does not recognise the proper entries in the xkb such as XF86Eject. It only seems to understand more simplified entries. Therefore I have mapped above all of the buttons to function keys, which KDE seems to understand up to some large number (I only hit 33 so probably higher than that).

I have not tested why this is the case (too much code, and coulnd not find anything on the net about it) and have not tested it against newer versions. This also applies for other keyboard mappings.

If for example you have a Microsoft Natural Keyboard (I used to have one at home) then it also fails because the keys are mapped to XF86Back, XF86Forward etc...

To fix this, you can just map them to function keys (F1..32 or more) as I have done above.

4 Page History

$Id: index.txt,v 1.4 2002/11/21 09:33:22 scottp Exp $