From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/6616 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: Setting up lbr fonts Date: Wed, 23 Jan 2002 09:54:07 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <5.1.0.14.1.20020123093117.033d0c00@server-1> References: <5.1.0.14.1.20020122132800.032ff078@server-1> <20020122114515.900@oxmail.ox.ac.uk> <5.1.0.14.1.20020122132800.032ff078@server-1> 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 1035397136 12192 80.91.224.250 (23 Oct 2002 18:18:56 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:18:56 +0000 (UTC) Cc: ConTeXt Original-To: Jens-Uwe Morawski In-Reply-To: <20020123024402.14904188.morawski@gmx.net> Xref: main.gmane.org gmane.comp.tex.context:6616 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:6616 At 02:44 AM 1/23/2002 +0100, Jens-Uwe Morawski wrote: >I know that ConTeXt prefers texfont.pl, but i hope fonts already >installed using fontinst can be covered too, since fontinst is >afaik the only way where i can substitute the numbers of a font with >its oldstyle variants (choosing pplj instead of pplx >gives me oldstyle numbers). > >I hope somebody has the time and can manage this. If you don't use texfont.pl, the main thing you need to do is to find out what the names are of the tfm's that fontinst generates. You can make typescripts as simple as you want, skipping symbolic names, or even not using typescript and using \definefont directly, but then you loose a couple of abstractions. Say that you have this palatino and that you used fontinst to generate ec encoded fonts, then you have to make a script like: \starttypescript [serif] [adobepalatino] [ec] \definefontsynonym [Palatino] [thefontinstgeneratedname] \definefontsynonym [PalatinoBold] [anotherfontinstgeneratedname] \stoptypescript It's a serif font, so now we define an accompanying serif script: \starttypescript [serif] [adobepalatino] [name] \definefontsynonym [Serif] [Palatino] \definefontsynonym [SerifBold] [PalatinoBold] \stoptypescript Say that you put these script in a file called typeface.tex that you put somewhere where tex can find it. In your document (or style) you now need to tell context that you need this file: \usetypescriptfile[typeface] you will probably have a map file too and you can either load that one in pdftex.cfg or let context do that. The next thing is using this font. Of course you can execute typescripts yourself but best is to use the command \definetypeface [myface] [rm] [serif] [adobepalatino] [default] [encoding=ec] this means as much as: create a typeface, map it to the rm families, using the serif definitions of adobepalatino matching encodning ec, and use the default size definition scripts. In a similar way you can add ss, tt, mm, etc definitions to this typeface 'myface'. Bewaqre, use rscale=... to achieve relative scaling, if needed. Now you need to activate this typeface (because each typeface has its own namespace, you can mix 'm any way you want] \setupbodyfont[myface,10pt,rm] Now you should have an adobe palatino document. If you do it this way, you can also say (handy for titlepages and so): {\definedfont[SerifBold at 60pt]This is a big title} or \definefont[VeryBigFont][Palatino at 150pt] \VeryBigFont Guess what (happens after \setuphead[chapter][style=VeryBigFont]) Now, the whole idea behind this concept is that you can build your own set of definitions (typefaces); here we have for instance one typeface.tex file per project and a couple of general system wide ones for ourself. Back to texfont vs fontinst: in the case of texfont, you can more conveniently mix multiple instances, like three regular weights of a multipel master, or seven different slanted palatino's; in the case of fontinst you have the advantages you already mentioned, but you're on your own to figure out what file names are used as well as prevent nameclashes yourself]. BTW, does patrick still has this idea of reprogramming those font tools? 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 ------------------------------------------------------------------------- fall-back web server: www.pragma-pod.nl -------------------------------------------------------------------------