Xref: utzoo comp.windows.open-look:69 alt.sys.sun:2000
Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!decwrl!infopiz!lupine!ncd.com
From: jim@ncd.com (Jim Fulton)
Newsgroups: comp.windows.open-look,alt.sys.sun
Subject: Re: shelltool/cmdtool dumping core
Summary: font name glitches
Message-ID: <2570@lupine.NCD.COM>
Date: 12 Nov 90 19:49:34 GMT
References: <ROBERTS.90Nov6151946@studguppy.lanl.gov> <1990Nov11.165348.10554@zorch.SF-Bay.ORG>
Sender: jim@NCD.COM
Followup-To: comp.windows.open-look
Distribution: comp
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 29

> ;"XView warning: Cannot load font '-sun-open look glyph-----*-180-*-*-*-*-*-*'
> ; (Font package)
> ;XView error: Unable to fined OPEN LOOK glyph font (Panel package)"
> ;
> 
> What you have found is something I am rather shocked the MIT dudes have not
> yet fixed.

What bug?  The font is simply not one of those donated to MIT.  There's
a 19pt, but not an 18pt:

% cd /x/fonts/bdf/misc/
% egrep '^FONT ' ol*.bdf
olcursor.bdf:FONT -Sun-OPEN LOOK cursor-----12-120-75-75-P-160-SunOLcursor-1
olgl10.bdf:FONT -Sun-OPEN LOOK glyph-----10-100-75-75-P-101-SunOLglyph-1
olgl12.bdf:FONT -Sun-OPEN LOOK glyph-----12-120-75-75-P-113-SunOLglyph-1
olgl14.bdf:FONT -Sun-OPEN LOOK glyph-----14-140-75-75-P-128-SunOLglyph-1
olgl19.bdf:FONT -Sun-OPEN LOOK glyph-----19-190-75-75-P-154-SunOLglyph-1


> The problem is in the whitespace character in the font name.

Why?  Whitespace characters are legal in font names.

If the '-sun-open look glyph-----*-180-*-*-*-*-*-*' can't be changed through
resources or other configuration information, an entry in a fonts.alias file 
might work:

"-sun-open look glyph-----18-180-75-75-p-154-sunolglyph-1" "-sun-open look glyph-----19-190-75-75-p-154-sunolglyph-1"