Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!ucsd!ucbvax!ucdavis!csusac!unify!openlook!openlook-request
From: kasso@Eng.Sun.COM (Chris Kasso)
Newsgroups: comp.windows.open-look
Subject: Re: shelltool/cmdtool dumping core
Message-ID: <890ykj4@openlook.Unify.Com>
Date: 12 Nov 90 19:16:18 GMT
Lines: 29


  From:  asgard@zorch.SF-Bay.ORG (J.R. Stoner)
  Date:  11 Nov 90 16:53:48 GMT

  What you have found is something I am rather shocked the MIT dudes have not
  yet fixed.  The problem is in the .bdf file distributed with the MIT release.
  
  The problem is in the whitespace character in the font name.  It seems that
  the OLGx fonts and all New Century fonts have whitespace characters in the
  name definition in the BDF file.

This is not a problem.  The 1.3 version of the XLFD spec requires whitespace
to separate words in the family name.  From sec 3.1.2.2...

``FAMILY_NAME is a string that identifies the range of ``family'' of typeface
designs that are all variations of one basic typographic style.  This must be 
spelled out if full, with words separated by spaces as required...''
  
				   If you go to the source, change the appropr
  line in the file to something like '-' or '_', rerun bdftosnf, install into
  /usr/lib/X11/fonts/misc (or whereever), then restart the server Xsun will not
  barf on attempts to load the font.

Adding ``-'' to the name will change the meaning since the spec defines
``-'' as field sperators.

Chris Kasso					Internet: kasso@Eng.Sun.COM
Windows and Graphics Software			uucp: {...}!sun!kasso
Sun Microsystems, Inc.