From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/8235 Path: main.gmane.org!not-for-mail From: Randall Skelton Newsgroups: gmane.comp.tex.context Subject: Re: Yet another font problem... Date: Mon, 10 Jun 2002 17:33:19 +0100 (BST) Sender: owner-ntg-context@let.uu.nl Message-ID: References: <20020610101359.653ac514.wmcclain@salamander.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1035398654 25769 80.91.224.250 (23 Oct 2002 18:44:14 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:44:14 +0000 (UTC) Cc: Original-To: Bill McClain In-Reply-To: <20020610101359.653ac514.wmcclain@salamander.com> Xref: main.gmane.org gmane.comp.tex.context:8235 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:8235 Thank you Bill for all your comments and for putting up your original notes on the web. I (finally) have my type1 font installed... One down, 10 more to go. It turns out one of the larger problems that I had was that the original font file is for the Mac (ClassicOS) and I am now using OS X. Of course, OS X still uses the HFS+ file system so it is fundamentally case insensitive. When I generated the .pfb and .tfm file from my Mac font suitcase, it spat out files with 'A Banshee' as the name. I immediately removed the 'A ' as having a space in the font filename broke most of the context perl scripts. However, I left the capital 'B' and ended up with Banshee.pfb, Banshee.afm, texnansi-Banshee.tfm, texnansi-raw-Banshee.tfm, and texnansi-adobe-banshee.map. I don't exactly understand why, but renaming the fonts to lowercase 'banshee' and re-running texfont seems to have fixed many of the problems I was having. Thanks again for all your help Bill! Cheers, Randall On Mon, 10 Jun 2002, Bill McClain wrote: > > I now have the font example working... whew! I do see a large number > > of warnings of the form, "Warning: pdfetex (file > > /Users/mek/Local/texmf/pdftex/config/context/pl0-am s-cmr.map): entry > > for`plb10' already exists, duplicates ignored," but I get the correct > > fonts in the end. Should I see these warnings? > > I see similar warnings. I believe they can be eliminated by messing with > map files or pdftex.cfg, but I have never bothered. As long as the > warnings don't reference fonts you are using... > > > My problem was simply that I became confused when I found two > > occurances of 'cont-sys': > > > > $texroot/texmf/tex/context/user/cont-sys.rme > > $texroot/texmf/tex/context/base/cont-sys.ori > > > > Why are there two of these? Surely I do not need two copies of the > > same file (I originally only modified the .ori file). For my own > > reference, in which directory should I put 'texexec.ini' and > > 'cont-sys.ini'? Should they go where the stock .rme files are? (i.e. > > $texroot/texmf/context/config and $texroot/texmf/tex/context/user) > > I don't know why there are multiple named versions. On my system: > > /usr/share/texmf/context/config/texexec.ini > cont-sys.ini : I don't have it > > > In the case of setting up a script font that only has one typeface > > (i.e. no bold, italic font, small caps, etc...) how do I go about > > setting up a type-banshee.tex file? My first attempt reads: > > The script looks ok to me and your map file is being found and used. > Does texnansi-banshee.tfm exist? Your \definesynonym statements must > eventually refer to a .tfm name that exists in some map file that the > job knows about. > > If it does exist, have you run texhash since installing it? (That's my > favorite forgotten step). > > If so, search for more errors in the log that mention texnansi-banshee. > > -Bill > -- > Sattre Press The King in Yellow > http://sattre-press.com/ by Robert W. Chambers > info@sattre-press.com http://kiy.sattre-press.com/ >