From: "John R. Culleton" <john@wexfordpress.com>
Subject: Installing Truetype fonts in context.
Date: Sat, 4 Jun 2005 14:21:46 +0000 [thread overview]
Message-ID: <200506041421.47001.john@wexfordpress.com> (raw)
--Like a good little TeXer I have always avoided Truetype fonts.
But now I have a situation where the customer is requesting it,
and has provided the font. So I have tried to follow the
instructinns in the pdftex manual as well as those in Texfont
Explained manual. First I got apparently clean results but the font
looks just like Computer Modern. The only error message I can
see is one asking for a pfb file which of course I don't have.
Then following an earlier post I tried something like this. The font
is a Devangari font, or perhaps more properly a Western font that
looks a bit like Devnagari script. Here is my run script:
-----------------------------------------------------
ttf2afm -e 8r.enc -o ds_izmir.afm ds_izmir.ttf
texfont --en=8r --ve=truetype --co=all --makepath --install
cd /usr/share/texmf-local/fonts/map/pdftex/context/
cat *map >plus.map
mv plus.map /usr/share/texmf/fonts/map/pdftex/updmap
updmap
texhash
-----------------------------------------------------------
With this run stream texfont has two complaints: first that it is an unknown
vendor and
second that it cannot find either a pfa or pfb file.
There is a trick to it I am sure, and I am sure I do not know the
trick.
John Culleton
The answers to all your publishing questions are found
in the excellent books listed in the word-famous shortlist!
http://wexfordpress.com/tex/shortlist.pdf
next reply other threads:[~2005-06-04 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 14:21 John R. Culleton [this message]
2005-06-04 19:28 ` Thomas A. Schmitz
2005-06-04 21:34 ` Hans Hagen
2005-06-05 11:46 ` John R. Culleton
2005-06-06 10:08 ` John R. Culleton
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=200506041421.47001.john@wexfordpress.com \
--to=john@wexfordpress.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).