Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!mcvax!enea!erix!erisun!hans
From: hans@erisun.UUCP (Hans J. Albertsson)
Newsgroups: comp.windows.x
Subject: X11 CapsLock sillyness
Message-ID: <1116@erisun.UUCP>
Date: Sat, 10-Oct-87 19:59:38 EDT
Article-I.D.: erisun.1116
Posted: Sat Oct 10 19:59:38 1987
Date-Received: Tue, 13-Oct-87 01:39:27 EDT
References: <1114@erisun.UUCP> <1115@erisun.UUCP>
Reply-To: hans@erisun.UUCP (Hans J. Albertsson)
Organization: Ericsson Information Systems Sverige AB, Bromma, Sweden
Lines: 18

I was wondering about how an X server and/or its clients know what keysyms are
upper/lower case pairs. Being of a Swedish persuasion, I'd like to consider
`\' to be the upper case of `|', and was wondering how to encourage CapsLock
to have its way with these two.  After looking desperately for some time, I
finally did manage to find out. Let me say right away, I really had hoped it
wouldn't be like this; In XKeyBind.c I find the following:

			if (usymbol >= XK_A && usymbol <= XK_Z)

which is how X determines what KeySyms are affected by CapsLock.

Yeah. Can YOU spell  E-T-H-N-O-C-E-N-T-R-I-C??????

P.S. I know, I should use the pair XK_Odiaeresis/XK_odiaeresis, which are
defined, but they're unlikely to have the proper attention paid to their
relationship by the above code fragment either, are they? And, there
are no fonts for those. I sincerely hope that this part of X11 really
IS "under construction"...