From: "Duncan Hothersall" <dh@capdm.com>
Cc: "ConTeXt mailing list" <ntg-context@ntg.nl>
Subject: RE: Introducing new fonts
Date: Wed, 20 Jun 2001 17:00:43 +0100 [thread overview]
Message-ID: <MFEFJNAPONLOLJPIHFBIGEIJCFAA.dh@capdm.com> (raw)
In-Reply-To: <3.0.6.32.20010620173722.0149d310@server-1>
> 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
prev parent reply other threads:[~2001-06-20 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 14:48 Duncan Hothersall
2001-06-20 15:37 ` Hans Hagen
2001-06-20 16:00 ` Duncan Hothersall [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MFEFJNAPONLOLJPIHFBIGEIJCFAA.dh@capdm.com \
--to=dh@capdm.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).