[PLUG] keyboard mapping change

[Denis Heidtmann]

On the back it says SOFT F-21YQ (SPK-2000).   It has a "Fujitsu
computers Siemens" label on the front. I cannot find a good picture to
show the key layout.

Searching for that name (SOFT...) I get some hits for BIOSTAR stuff.
It may be a designation for an entire system.

-Denis

On Mon, Oct 27, 2014 at 1:41 PM, Ronald Bynoe <ronald at bynoe.us> wrote:
> What make/model keyboard is it? I'd be interested to see an image of it
> Online.
> On Oct 27, 2014 1:08 PM, "Denis Heidtmann" <denis.heidtmann at gmail.com>
> wrote:
>
>> On Mon, Oct 27, 2014 at 11:42 AM, Dale Snell <ddsnell at frontier.com> wrote:
>> > On Mon, 27 Oct 2014 10:31:48 -0700
>> > Denis Heidtmann <denis.heidtmann at gmail.com> wrote:
>> >
>> >> showkey -a
>> >> for the left key of interest:
>> >> <   60 0074 0x3c
>> >> for  the right key of interest:
>> >> \   92 0134 0x5c
>> >
>> > This is showing the ASCII values for the characters in decimal,
>> > octal, and hexadecimal.  "<" is 60 (dec), \074 (oct), and 0x3c
>> > (hex); "\" is 92 (dec), \134 (oct), and 0x5c (hex).  Note that
>> > this information doesn't do you much good if you're going to
>> > modify your console keymap.  You'll need to uses the -k or -s
>> > options to showkey.
>> >
>> >
>> >> There is also xev:
>> >>
>> >> For the left key:
>> >> KeyPress event, serial 36, synthetic NO, window 0x4c00001,
>> >>     root 0x261, subw 0x0, time 2468220, (18,-5), root:(1517,42),
>> >>     state 0x10, keycode 94 (keysym 0x3c, less), same_screen YES,
>> >>     XLookupString gives 1 bytes: (3c) "<"
>> >>     XmbLookupString gives 1 bytes: (3c) "<"
>> >>     XFilterEvent returns: False
>> >>
>> >> KeyRelease event, serial 36, synthetic NO, window 0x4c00001,
>> >>     root 0x261, subw 0x0, time 2468668, (18,-5), root:(1517,42),
>> >>     state 0x10, keycode 94 (keysym 0x3c, less), same_screen YES,
>> >>     XLookupString gives 1 bytes: (3c) "<"
>> >>     XFilterEvent returns: False
>> >>
>> >> For the right key:
>> >> KeyPress event, serial 36, synthetic NO, window 0x4c00001,
>> >>     root 0x261, subw 0x0, time 2474140, (18,-5), root:(1517,42),
>> >>     state 0x10, keycode 51 (keysym 0x5c, backslash), same_screen YES,
>> >>     XLookupString gives 1 bytes: (5c) "\"
>> >>     XmbLookupString gives 1 bytes: (5c) "\"
>> >>     XFilterEvent returns: False
>> >>
>> >> KeyRelease event, serial 36, synthetic NO, window 0x4c00001,
>> >>     root 0x261, subw 0x0, time 2474396, (18,-5), root:(1517,42),
>> >>     state 0x10, keycode 51 (keysym 0x5c, backslash), same_screen YES,
>> >>     XLookupString gives 1 bytes: (5c) "\"
>> >>     XFilterEvent returns: False
>> >>
>> >> These results do not seem to say the same thing.  Confusion.
>> >
>> > The xev results are not guaranteed to match the showkey results.
>> > In this particular case, they do.  Note the numeric values for
>> > XLookupString and XmbLookupString: 3c and 5c.  These are, again,
>> > the ASCII values for the given characters, "<" and "\"
>> > respectively.
>> >
>> > That said, I have to ask if you're sure you want to change these.
>> > Putting "<" and "\" next to the shift keys is not normal US
>> > keyboard layout.  Normally "<" is above the comma, and "\" is
>> > below the "|", next to the backspace key.  (The "\"/"|" key can be
>> > elsewhere; perhaps above the return key.  It depends on what kind
>> > of return key you have.  Mine is the large "L"-shaped variety.)
>> >
>> > Do you have "<" and "\" elsewhere on your keyboard?  If not, you
>> > do NOT want to change these values.
>> >
>> > --Dale
>>
>> This kb has a slightly different layout than what I am used to.  There
>> is an extra key (#94) crammed into next to the left shift key.  It is
>> labeled pipe and backslash.  It produces greater than and less than.
>> Those symbols are also generated by shift coma and shift period.  And
>> my shift finger keeps hitting that crammed-in #94 key.  (I see now
>> that I do not want to change #51, as that is the only key producing
>> pipe.  So only # 94 needs changing.)
>>
>> I still need a place to put the instruction to  change #94.
>>
>> My other solution to this problem is to return to Free Geek and do a
>> more thorough inspection while selecting a keyboard.
>>
>> -Denis
>> _______________________________________________
>> PLUG mailing list
>> PLUG at lists.pdxlinux.org
>> http://lists.pdxlinux.org/mailman/listinfo/plug
>>
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug