From: Matt Gushee <mgushee@havenrock.com>
Subject: SOLVED -- Re: pdfetex can't find map files
Date: Fri, 10 Dec 2004 18:11:04 -0700 [thread overview]
Message-ID: <41BA4928.7020106@havenrock.com> (raw)
In-Reply-To: <41B64F52.6010109@havenrock.com>
Matt Gushee wrote:
> Warning: pdfetex (file original-public-vnr.map): \
> cannot open font map file
>
> The files exist and are world-readable, so the above must mean that
> pdfetex just can't find them.
Thomas Esser has explained that pdfetex uses $TEXPSHEADERS (or maybe
$PSHEADERS) as the search path for map files. So I added
$TEXMF/fonts/map//
to TEXPSHEADERS in my texmf.cnf, and now everything works fine.
It seems a little strange that pdf(e)tex doesn't use TEXFONTMAPS. Maybe
it will in the future? Perhaps Hans can comment on that.
Thanks to all.
--
Matt Gushee
Englewood, CO, USA
prev parent reply other threads:[~2004-12-11 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 0:48 Matt Gushee
2004-12-08 10:39 ` Patrick Gundlach
2004-12-08 13:58 ` Matt Gushee
2004-12-08 14:09 ` Patrick Gundlach
2004-12-08 23:23 ` Matt Gushee
2004-12-11 1:11 ` Matt Gushee [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=41BA4928.7020106@havenrock.com \
--to=mgushee@havenrock.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).