You can define the actions of individual keys in addition to or instead of using the "K" option in the Braille configuration string to enable the whole keyboard at the same time as a Braille input key set.
To map individual keys, use the "K" setup directive. This is a general setup directive to WTC, uppercase "K", as opposed to the uppercase "K" that is included in the Braille keyboard driver configuration substring to enable the standard keyboard as a whole in addition to the Braille keys.
The "K" setup directive enables you to define key mappings on an individual basis. if you use this directive without enabling the standard keyboard with the "K" option in the Braille keyboard substring, you start with a keyboard which is mostly disabled. If you do use the "K" option in the Braille keyboard definition, you start with a fully enabled keyboard. Although individual key maps[pings are provided via a general WTC setup directive, they are processed only if a Braille input keyboard is enabled, but it is possible to not actually define a Braille input key set in order to facilitate a standard keyboard with custom mappings.
The syntax of the "K" directive is as follows. The letter "K" is followed by a sequence of hexadecimal number pairs, each number having exactly 2 digits (leading 0 if necessary). The first number in each pair is the virtual key code of the key that is to be translated (mapped), and the second number is the virtual key code of the key that it is to represent (be mapped to). For example:
"K304A"
would result in the number 0 producing a letter "j".
Use "00" as the translation to disable an individual key, making it completely inactive. You can determine the virtual key codes to use with the keyboard information utility on the directory dialling/setup menu.
Because the keyboard mappings are only used if a Braille keyboard is enabled, they can be active locally or globally like the Braille input key set itself.
Page url: http://wtcmanual.wintextware.com/index.html?bti_defining_a_user_key_map.htm