From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/4855 Path: main.gmane.org!not-for-mail From: "Duncan Hothersall" Newsgroups: gmane.comp.tex.context Subject: RE: Introducing new fonts Date: Wed, 20 Jun 2001 17:00:43 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: References: <3.0.6.32.20010620173722.0149d310@server-1> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035395491 29304 80.91.224.250 (23 Oct 2002 17:51:31 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:51:31 +0000 (UTC) Cc: "ConTeXt mailing list" Original-To: "Hans Hagen" In-Reply-To: <3.0.6.32.20010620173722.0149d310@server-1> Xref: main.gmane.org gmane.comp.tex.context:4855 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:4855 > vf is a font issue not a context issue, actualy it's a dvi/pdf driver > issue; normally using an texnansi encoding vector when applying afm2tfm > works good; I lazily picked up the tfm and vf files from CTAN since they already existed. I'll regenerate them locally and see if that helps. Sigh, haven't done this for years... now how does afm2tfm work again... > did you put the vf's in the right place? did you run mktexlsr? Yes, and yes. > i have a perl script that can be of help and the font manual says some > things [although most of th emanual concerns the new type face layer] I'd welcome anything that might be of help, because once I've regenerated the TFMs etc. I am stalled. Many thanks for anything you can offer, Duncan