From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/5239 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: fonts / proposal Date: Wed, 08 Aug 2001 14:13:06 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <5.1.0.14.1.20010808140748.02358f98@server-1> References: <3B6FA974.7DBA7E50@elvenkind.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Trace: main.gmane.org 1035395842 32416 80.91.224.250 (23 Oct 2002 17:57:22 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:57:22 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: siep@elvenkind.com In-Reply-To: <200108081029.MAA03257@plane.elvenkind.com> Xref: main.gmane.org gmane.comp.tex.context:5239 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:5239 At 11:34 AM 8/8/2001 +0200, siep@elvenkind.com wrote: >dvips reads psfonts.map to find the PostScript font for a given tfm, >plus any transformations that have to be applied to that file. You >can have as many tfms as you like for one PostScript font. For this, >you can simply add a bunch of (Context) tfm-s to an existing >psfonts.map and since the new tfm names are different from existing >tfm names, it won't upset existing usage. right, i'm now using a psfonts.map file with all names stripped out [second entry] in which case it does not conflict. for the sake of simplicity, i furthermore leave that file untouched >The tricky part is reverse lookup. I understand from Taco that this >occurs when a to-be-included epsfile needs fonts. Here, additional >mapfile entries can cause problems. I am not familiar with the >details. However, offhand I would say that for reverse lookup only >the PostScript fontname and the filename would be used, and that >there should be no problems as long as all entries referring to the >same PostScript fontname also refer to the same pfb. It shouldn't be >that hard to write a script which validates and corrects mapfiles for >this. right, with reverse lookup, the FontName is used, unless removed. Since this name has no info on shape changes or alike, i removed them, otherwise pdftex will start loading the associated tfm file [funny confusing messages about fonts you don't use then show up] -) >The point of all this is that it should be possible to stuff everything >you need in your default psfonts.map. it would be a nice option [i will discuss this with thanh] if entries could be overloaded >Also a word about fontinst. If you read the documentation then it is >very LaTeX-centric. I believe however that this is mainly true for the >top-level commands. I created three testfonts with fontinst, all based >on Helvetica Light, with the following input file: ok, thanks for testing, i will look into that when i'm back from tug2001 Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com -------------------------------------------------------------------------