From: Matt Gushee <mgushee@havenrock.com>
Subject: Re: Re: pdfetex can't find map files
Date: Wed, 08 Dec 2004 16:23:34 -0700 [thread overview]
Message-ID: <41B78CF6.1060409@havenrock.com> (raw)
In-Reply-To: <m2is7c3mqr.fsf@levana.de>
Patrick Gundlach wrote:
> The cont-sys.tex is not installed by default. You have to copy
> cont-sys.ori or cont-sys.rme to cont-sys.tex.
Yes, I know that. Of course, I could have forgotten, but I didn't this time:
$ find /usr/local/share/texmf -name cont-sys.tex
/usr/local/share/texmf/tex/context/base/cont-sys.tex
$ kpsewhich cont-sys.tex
/usr/local/share/texmf/tex/context/base/cont-sys.tex
$ grep mapfiles /usr/local/share/texmf/tex/context/base/cont-sys.tex
\autoloadmapfilestrue
% \resetmapfiles \usetypescript [map] [base] [all]
\resetmapfiles
So, unfortunately, the answer is not quite that simple.
I notice in your post on the teTeX list that your cont-sys.tex
explicitly loads a couple of map files. At first glance that doesn't
seem related, but do you think it might be?
You know, I have a feeling this is really a problem with pdftex--either
an error in my texmf.cnf or a software bug. I have previously had
problems with pdftex failing to find resources in $TEXMFLOCAL; in the
past I have worked around this by moving files into $TEXMFMAIN, but I
want to avoid that if at all possible--I use the teTeX package from my
Linux distribution, and I'm tired of having my changes overwritten every
time I upgrade.
So, I appreciate your help so far. Still looking for a solution ...
--
Matt Gushee
Englewood, CO, USA
next prev parent reply other threads:[~2004-12-08 23:23 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 [this message]
2004-12-11 1:11 ` SOLVED -- " Matt Gushee
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=41B78CF6.1060409@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).