From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3C5FC5E3.1B1A7F9F@strakt.com> From: Boyd Roberts MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] "a pox on the things." [uk keyboards] References: <20020205112826.5461c636.matt@proweb.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 5 Feb 2002 12:45:39 +0100 Topicbox-Message-UUID: 4bc9e8fc-eaca-11e9-9e20-41e7f4b1d025 Matt H wrote: > but can't find out how to stop having to search my kb for the characters Have you seen the /dev/kbmap stuff? KBMAP(3) KBMAP(3) NAME kbmap - keyboard map SYNOPSIS bind -a #Io /dev /dev/kbmap DESCRIPTION The kbmap device serves a one-level directory containing a single file, kbmap, representing the kernel's mapping of keyboard scan codes to Unicode characters (see cons(3) and keyboard(6)). Reads return the current contents of the map. Each entry is one line containing three 11 character numeric fields, each followed by a space: a table number, an index into the table (scan code), and the decimal value of the corre- sponding Unicode character (0 if none). The table numbers are platform dependent; they typically distinguish between unshifted and shifted keys. The scan code values are hardware dependent and can vary from keyboard to keyboard. Writes to the file change the map. Lines written to the file must contain three space-separated numeric fields, representing the table number, scan code index, and Uni- code character. Values are taken to be decimal unless they start with 0x (hexadecimal) or 0 (octal). The Uni- code character can also be represented as 'x where x gives the UTF-8 representation of the character (see utf(6)). Entries in the Unicode `private use' area from +U'FD80' to +U'FDFF' might have special meaning to some keyboard drivers and should not be mapped (or remapped) lightly. SEE ALSO cons(3), keyboard(6), utf(6)