From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: pdfetex cannot find map files
Date: Wed, 17 May 2006 13:25:14 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0605171321410.2968@nqvgln> (raw)
In-Reply-To: <Pine.WNT.4.63.0605171241120.2968@nqvgln>
On Wed, 17 May 2006, Aditya Mahajan wrote:
>
>> Aditya Mahajan wrote:
>>> The problem of "cannot open font map file" is still there. I deleted
>>> all existing context trees from my computer and downloaded the
>>> mswincontext.zip (dt. 2006-05-17) from Pragma's website. When I run a
>>> simple
>>> \starttext Hello World \stoptext
>>> file, I get
>>> [log snipped]
> On Wed, 17 May 2006, Hans Hagen wrote:
>> here i get for
>>
>> \starttext test \stoptext:
>>[log snipped]
>> did you run setuptex.bat beforehand?
>
>
> Yes, I did. I do not keep texmfstart in my path to prevent running
> context without sourcing setuptex.
>
> I also tried this by running, cscite.bat and compiling the file
> through scite. I get the same error message.
>
> Is it possible that the wrong texmf.cnf is loaded (as Taco pointed
> out). There is one at texmf/web2c also. setuptex sets TEXMFCNF to
>
> F:\tmp\mp>echo %TEXMFCNF%
> E:\isoimage\usr\local\context\tex\texmf{-local,}/web2c
>
> I changed that to
> .......\tex\texmf-local\web2c, but still get the same error.
>
>
> Context can locate the files
>
> F:\tmp\mp>texmfstart --locate original-empty.map
> E:/isoimage/usr/local/context/tex/texmf-local/fonts/map/dvipdfm/context/original
> empty.map
>
> but can not open it. I even tried a chmod 755 -R isoimage, but that
> did not help.
>
> How can I debug why pdfetex is not able to *open* the map files?
Well, there was something in the path that was interfering with
context.
set PATH=E:\Ruby\bin
E:\isoimage\usr\local\context\tex\setuptex.bat E:\isoimage\usr\local\context\tex
works correctly. I do not know what was interfering, I'll look into
everything in my path one by one see what was going wrong.
Sorry about all the noise.
Aditya
next prev parent reply other threads:[~2006-05-17 17:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 18:50 Trouble with new update Aditya Mahajan
2006-05-11 18:54 ` Hans Hagen
2006-05-11 19:05 ` Aditya Mahajan
2006-05-11 20:10 ` Hans Hagen
2006-05-11 21:38 ` Aditya Mahajan
2006-05-11 19:08 ` Thomas A. Schmitz
2006-05-11 19:11 ` Aditya Mahajan
2006-05-17 16:25 ` pdfetex cannot find map files Aditya Mahajan
2006-05-17 16:34 ` Taco Hoekwater
2006-05-17 16:34 ` Hans Hagen
2006-05-17 16:59 ` Aditya Mahajan
2006-05-17 17:25 ` Aditya Mahajan [this message]
2006-05-17 20:22 ` Hans Hagen
2006-05-17 20:32 ` Aditya Mahajan
2006-05-17 21:06 ` Hans Hagen
2006-05-17 22:43 ` Aditya Mahajan
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=Pine.WNT.4.63.0605171321410.2968@nqvgln \
--to=adityam@umich.edu \
--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).