Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: need help to add accented letters to US keyboard
Message-ID: <9010121229.AA01547@expire.lcs.mit.edu>
Date: 12 Oct 90 12:29:36 GMT
References: <9010120141.AA01273@lightning.McRCIM.McGill.EDU>
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 16


    The problem is that keysyms after the first two in a key binding do not
    have standard interpretations,

Incorrect.  A standard interpretation was introduced in R4.

    I seem to recall that there is some sort of de-facto
    pseudo-standard that the third keysym is to be used when Mod1 is
    active, but I don't think the default XLookupString() does this;

There is a standard interpretation for a "group" modifier, and the
R4 XLookupString implements it.

    Keyboard handling is IMO one of the weakest points of X.

It could certainly be improved, no question.