I am having a problem with the high order bit of a character being 
clipped when entered in an xterm window under motif. I have reprogrammed
the F1 key to transmit a <ff> <be> character sequence by using the
following line in .Xdefaults:

~Ctrl ~Shift ~Alt <Key> F1 : string(0xff) string(0xbe) \n\

I merge in this line with xrdb -merge and then create the new xterm
which has the remapped F1 key. The problem that arises is that the 
application which is recieving input at the time only sees a <7f> <3e>
sequence, which is <ff> <be> with the high order bit of each
character being filtered or ignored.

When I run xev and press the F1 key, I get the correct value showing 
up in the following two key events:

  KeyPress event, serial 14, synthetic NO, window 0x2800001,
  root 0x28, subw 0x0, time 2067815294, (67,80), root:(74,104),
  state 0x0, keycode 16 (keysym 0xffbe, F1), same_screen YES,
  XLookupString gives 0 characters:  ""

  KeyRelease event, serial 16, synthetic NO, window 0x2800001,
  root 0x28, subw 0x0, time 2067815406, (67,80), root:(74,104),
  state 0x0, keycode 16 (keysym 0xffbe, F1), same_screen YES,
  XLookupString gives 0 characters:  ""

Notice that the keysym being transmitted is correct; 0xffbe.
But when I use the F1 key while in vi or in a program I wrote to 
spit back the hex values of keyboard input, I only get <7f> <3e>.

Does anyone know why the high order bit is being filtered and what
I can do to make sure that the entire 8bits make it through to
the final application? Any help is greatly appreciated.

Please *email* any responses.