Path: utzoo!utgpu!watserv1!watmath!att!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: Guidelines for adding KeySyms?
Message-ID: <9004122226.AA16072@expire.lcs.mit.edu>
Date: 12 Apr 90 22:26:30 GMT
References: <16442@haddock.ima.isc.com>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 21


    There appears to be some
    mention of turning the 29th bit on, but I can't seem to determine if
    this is for registered or unregistered vendor-specific keysyms.

The 29th bit is for private keysyms, whether registered or not.

    If these keysyms are just for nameless function keys, should they be
    registered, or doesn't it matter in that case?

If you want to encourage other companies with similar function keys
to use the same keysym values, or you want to attempt to ensure that
other companies won't use the same values for different semantics,
then you should register the keysyms.

    If the 29th bit is to be turned on, is it proper to have byte 3 == 0xFF
    or should some new sequence be used? If the former, is it OK to have the
    lower 16 bits of the new keysyms clash with existing keysyms in the Misc
    set as long as the upper 16 bits don't?

Private is private, the bits are your business.