Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!smsc.sony.com!dce
From: dce@smsc.sony.com (David Elliott)
Newsgroups: comp.windows.x
Subject: Re: Client Ethics/Etiquette
Message-ID: <1991Feb13.153303.21308@smsc.sony.com>
Date: 13 Feb 91 15:33:03 GMT
References: <1991Feb8.191904.14630@ux1.cso.uiuc.edu>
Sender: dce@smsc.sony.com (David Elliott)
Reply-To: dce@smsc.sony.com (David Elliott)
Organization: Sony Microsystems, San Jose, CA
Lines: 29


In article <1991Feb8.191904.14630@ux1.cso.uiuc.edu>, ejk@ux2.cso.uiuc.edu (Ed Kubaitis) writes:
|> I recently ran into a problem involving my NCD 19 X-Terminal and the
|> InfoExplorer X application running on IBM RS/6000 AIX 3.1-3003. Part
|> of the problem is that InfoExplorer resets (and does not restore) the 
|> server font-path to include a directory that will be found on IBM AIX 
|> 3.1 systems. Another part of the problem seems related to its doing an 
|> "xrdb -load".

Neither of these are reasonable for the program to be doing.

The font path stuff is a little more forgivable, since there's often
no other way to easily handle special fonts.  Too bad X doesn't have
a way to create a font on the fly.  On the other hand, nobody should
ever "expect" a font to be in a specific place.

As for the xrdb -load thing, that's very anti-social.  Some people
don't use xrdb in the first place, so this just screws them up.  One
of the Motif tests does (did?) this, and it's very annoying.

Sadly, you may not be able to "vote with your wallet" in this kind of
case, but at least the rest of us know to steer clear of InfoExplorer X
for the time being.

-- 
...David Elliott
...dce@smsc.sony.com | ...!{uunet,mips}!sonyusa!dce
...(408)944-4073
..."His lower lip waved poutily with defiance..."