Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zaphod.mps.ohio-state.edu!think.com!paperboy!osf.org!dbrooks
From: dbrooks@osf.org (David Brooks)
Newsgroups: comp.windows.x.motif
Subject: Re: osf Keysyms and a mild flame
Message-ID: <17298@paperboy.OSF.ORG>
Date: 14 Dec 90 16:32:33 GMT
References: <1990Dec14.145313.5210@watdragon.waterloo.edu> <1990Dec14.160932.27142@thyme.jpl.nasa.gov>
Sender: news@OSF.ORG
Reply-To: dbrooks@osf.org (David Brooks)
Organization: Open Software Foundation
Lines: 47

In article <1990Dec14.160932.27142@thyme.jpl.nasa.gov>, kaleb@thyme.jpl.nasa.gov (Kaleb Keithley	) writes:
|> In article <1990Dec14.145313.5210@watdragon.waterloo.edu> tbray@watsol.waterloo.edu (Tim Bray) writes:
|> >A few days back, I posted a query to this august form.  To summarize,
|> >after installing motif 1.1, my applications broke because they couldn't
|> >find the new 'osf*' motif keysyms.  Why, I wondered.  No response from
|> >the newsgroup.
|> 
|> I also rewound news and saw that David Brooks, one OSFs support people,
|> also posted a reply in comp.windows.x.motif.  One might wonder why he
|> didn't send you a direct response (maybe he did?) but the fact of the 
|> matter is, he tried.

Thankyou Kaleb.

Tim Bray also writes:

|> I must say that it is mildly irritating that nobody from OSF bothered
|> to respond to the original posting, when the problem is totally obvious once

This newsgroup and mailing list is not run by OSF, and has no formal
connection with OSF, although several of us try to keep up with it.
In particular, it isn't OSF's support channel.  With our limited
resources, we (try to) keep up with support requests from those of our
licensees who have paid for a support contract and then, if we have
the time, with people who address questions to us directly.  On top of
all that, we do answer questions in the public forums.  I must say that
it is mildly irritating to be criticized thus.

|> I am rather more heavily pissed that nowhere in the motif 
|> documentation (at least in a form accessible to grep(1)) is there any
|> info on how to make the osf* keysyms visible in the first place so that
|> the virtual bindings can start to take effect.

Assuming you are a source licensee, and you are in charge of
installing the system, the minimum you should do is read the release
notes; in particular section 6.3.1.

dbrooks@penge 510$ grep -i keysym ch06.ot toc.ot
ch06.ot:       ./lib/Xm/XKeysymDB contains OSF virtual keysyms.  If you
ch06.ot:       include the OSF keysyms, the installation procedure (make
toc.ot:           3.14  Mnemonic Type Changed to KeySym.............   3-7
toc.ot:                 6.3.1  XKeysymDB............................   6-4

-- 
David Brooks				dbrooks@osf.org
Systems Engineering, OSF		uunet!osf.org!dbrooks
"No, I didn't say I wanted a Bud light!!!" -- Oedipus