The "us" keyboard layout contains a mapping for keycode 86 (which seems not to correspond to any physical key on many US keyboards) to the ASCII character '<'. This mapping causes conflicts with the mapping for keycode 51, which also maps (with shift) to '<'. Change the keyboard mapping generator to choose the lowest keycode for each ASCII character as indicating the relevant mapping to use, on the basis that a lower keycode roughly indicates a "more normal" key. On a German keyboard, which has keys for both keycode 51 and keycode 86 present, this causes '<' to be remapped to ';', which is a closer match to typical user expectations. Reported-by: Sven Dreyer <sven@dreyer-net.de> Signed-off-by: Michael Brown <mcb30@ipxe.org>
42 lines
1.1 KiB
C
42 lines
1.1 KiB
C
/** @file
|
|
*
|
|
* "sg" keyboard mapping
|
|
*
|
|
* This file is automatically generated; do not edit
|
|
*
|
|
*/
|
|
|
|
FILE_LICENCE ( PUBLIC_DOMAIN );
|
|
|
|
#include <ipxe/keymap.h>
|
|
|
|
/** "sg" keyboard mapping */
|
|
struct key_mapping sg_mapping[] __keymap = {
|
|
{ 0x19, 0x1a }, /* Ctrl-Y => Ctrl-Z */
|
|
{ 0x1a, 0x19 }, /* Ctrl-Z => Ctrl-Y */
|
|
{ 0x21, 0x2b }, /* '!' => '+' */
|
|
{ 0x23, 0x2a }, /* '#' => '*' */
|
|
{ 0x24, 0x34 }, /* '$' => '4' */
|
|
{ 0x26, 0x2f }, /* '&' => '/' */
|
|
{ 0x28, 0x29 }, /* '(' => ')' */
|
|
{ 0x29, 0x3d }, /* ')' => '=' */
|
|
{ 0x2a, 0x28 }, /* '*' => '(' */
|
|
{ 0x2b, 0x60 }, /* '+' => '`' */
|
|
{ 0x2d, 0x27 }, /* '-' => '\'' */
|
|
{ 0x2f, 0x2d }, /* '/' => '-' */
|
|
{ 0x3c, 0x3b }, /* '<' => ';' */
|
|
{ 0x3d, 0x5e }, /* '=' => '^' */
|
|
{ 0x3e, 0x3a }, /* '>' => ':' */
|
|
{ 0x3f, 0x5f }, /* '?' => '_' */
|
|
{ 0x40, 0x22 }, /* '@' => '"' */
|
|
{ 0x59, 0x5a }, /* 'Y' => 'Z' */
|
|
{ 0x5a, 0x59 }, /* 'Z' => 'Y' */
|
|
{ 0x5c, 0x24 }, /* '\\' => '$' */
|
|
{ 0x5e, 0x26 }, /* '^' => '&' */
|
|
{ 0x5f, 0x3f }, /* '_' => '?' */
|
|
{ 0x79, 0x7a }, /* 'y' => 'z' */
|
|
{ 0x7a, 0x79 }, /* 'z' => 'y' */
|
|
{ 0x7c, 0x24 }, /* '|' => '$' */
|
|
{ 0x7d, 0x21 }, /* '}' => '!' */
|
|
};
|