Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!samsung!uakari.primate.wisc.edu!caen!news.cs.indiana.edu!bronze!copper!tsui From: tsui@copper.ucs.indiana.edu (Yufeng Tsui) Newsgroups: comp.sys.next Subject: Re: Fonts Message-ID: <1991Feb20.211532.29866@bronze.ucs.indiana.edu> Date: 20 Feb 91 21:15:32 GMT References: Sender: news@bronze.ucs.indiana.edu (USENET News System) Organization: Indiana University, Bloomington Lines: 32 In article ersys!drin@nro.cs.athabascau.ca (Adrian Smith) writes: >Once I have FontCollection2.0 installed as per the included Makefile, how >do I make the fonts accessible to my apps? Every time I try and use one >of the new fonts from within WriteNow or Ed (to name two examples), I get ><< unaccessible font >>. What am I doing wrong? I think you should run buildafmdir on the font directory. It extracts the fontnames and put it in .fontlist(or something similiar). After you run some applications, you will also notice that the .cache file is created. That probably means everytime you put some new fonts on there, you have to get rid of .cache and run buildafmdir again. > >On the subject of fonts, is there any reason why the afm directory under >/NextLibrary/Fonts in 2.0 has symbolic links to all the existing .afm >files? What does this do? I will guess it tries to make 2.0 compatible with 1.0 font directory format. Anyone know why "/usr/lib/NextStep/WindowServer -e start" does not work anymore under 2.0? It says window server can not open /dev/vid0... Thanks! --yufeng ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IIII Yufeng Tsui, UCS of Indiana University. Bloomington , IN 47405 UU II UU {att,ames,rutgers,purdue}!iuvax!copper!tsui U II U tsui@indiana.edu, tsui@wood4.ucs.indiana.edu (NeXT mail) U II U tsuiy@iubacs.bitnet (forwarded) UU ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IIII