From: Berend de Boer <berend@pobox.com>
Subject: Re: Getting the PDF postscript fonts to work
Date: 06 Feb 2003 08:07:27 +1300 [thread overview]
Message-ID: <877kce5yxc.fsf@dellius.nederware.nl> (raw)
In-Reply-To: <3E41048E.5060806@freemail.hu>
Nagy Bence <gimb@freemail.hu> writes:
> > Has anyone been able to use the standard PDF postscript fonts with
> > context? I recently upgraded to tetex 2.0, latest context, so had to
> > restart with the font stuff.
> > 1. After tinkering I could get the URW stuff working, but I want the
> > Adobe.
> I have the same problem, but I couldn't find the right solution and
> URW fonts doesn't work too.
OK, what to do:
1. Run texfont on context/data/type-tmf.dat like this:
texfont --encoding=texnansi --fontroot=/usr/share/texmf --batch type-tmf.dat
That should produce the right .tmf files.
2. In your cont-sys.tex (/usr/local/texmf/tex/context/cont-sys.tex)
have only the following:
====================
% This seems to be Hans preferred encoding
\setupencoding[\s!default=texnansi]
====================
No other \usesetypescript, or \setupencoding should be present.
3. If you run this test file:
====================
\setupbodyfont
[pos,10pt]
\starttext
hello world.
{\ss hello again!}
{\tt the end.}
\stoptext
====================
it should run fine, except pdf(e)tex complaining that it can't find
the fonts.
4. Add the following to pdftex/config/pdftex.cfg
====================
map +texnansi-bitstrea-charter.map
map +texnansi-public-antp.map
map +texnansi-public-antt.map
map +texnansi-urw-bookman.map
map +texnansi-urw-courier.map
map +texnansi-urw-helvetica.map
map +texnansi-urw-palatino.map
map +texnansi-urw-times.map
map +texnansi-urw-zapfchan.map
====================
These files should be in that directory if texfont has run correctly.
You can also use \autoloadmapfilestrue and put \loadmapfile in your
cont-sys it seems, but that gives you lots of warnings, so I don't
like that approach.
Let me know if you encounter any problem!
--
Live long and prosper,
Berend de Boer
next prev parent reply other threads:[~2003-02-05 19:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 7:45 Berend de Boer
2003-02-04 12:26 ` Hans Hagen
2003-02-04 17:41 ` Berend de Boer
2003-02-04 17:59 ` Hans Hagen
2003-02-04 18:03 ` Matt Gushee
2003-02-04 23:20 ` Jens-Uwe Morawski
2003-02-05 8:48 ` Hans Hagen
2003-02-05 12:55 ` Siep
2003-02-05 12:33 ` Nagy Bence
2003-02-05 17:45 ` Patrick Gundlach
2003-02-05 19:07 ` Berend de Boer [this message]
2003-02-05 20:50 ` Jens-Uwe Morawski
2003-02-06 9:42 ` Nagy Bence
2003-02-05 23:07 ` Nagy Bence
2003-02-06 1:43 ` Berend de Boer
2003-02-06 9:33 ` Nagy Bence
2003-02-06 10:11 ` Hans Hagen
2003-02-06 11:30 ` mari.voipio
2003-02-06 18:50 ` Henning Hraban Ramm
2003-02-07 8:27 ` Hans Hagen
2003-02-07 6:52 ` Berend de Boer
2003-02-06 10:03 ` Hans Hagen
2003-02-06 11:18 ` mari.voipio
2003-02-09 15:04 ` Thomas Esser
2003-02-06 10:06 ` Hans Hagen
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=877kce5yxc.fsf@dellius.nederware.nl \
--to=berend@pobox.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).