Re: Not all the way back

[David Arnold <darnold@northcoast.com>]

Hans, Christian,

>>I am not all the way back. That is, the current beta installation of
>>Context is not yet fully backward compatible. I've attached a small zip
>>file of a document I prepared last fall with a previous version of Miktex
>>and Context.
>>
>>After unzipping to a temp directory, type make.bat in the directory to run
>>the compile.
>>
>>Note that I am not getting a table of contents as I once did.
>
>Hm, i get a toc in the screen version, centered with nicely colored sections.
>
>can you see if the tuo is loaded [in log]?

I checked the log file and there is no mention of any tuo file getting
loaded. Christian, I've found a cure, which I'll describe here, in the
hopes that this will help with a more stable installation of Context in the
Miktex distribution.

Here, as I see it, may be the problem. Christian has taken texexec.rme,
renamed it to texexec.ini, and placed texexec.ini in \texmf\miktex\bin.
This, on the surface appears an excellent strategy, because during
installation of Miktex, the setup program automatically adds Miktex to the
path (in older installations of Miktex, this was probably the number one
source of problems for users, not adjusting their path after the
installation). However, Context users have traditionally added
\texmf\Context\perltk to their path (at least I have always done it this
way), because there are a number of perl files that the Context system uses
that are in that directory (fdf2tan.pl, makempy.pl, mptopdf.pl, texexec.pl,
texfont.pl, texshow.pl, and *MOST* importantly in this case, texutil.pl.
Many of us use the runperl.exe wrapper. For example, I change runperl.exe
to mptopdf.exe, etc. Basically, I runperl.exe to filename.exe for each of
the above mentioned filename.pl.

Well, to make a long story short, I cut texexec.ini, texexec.exe from
\texmf\miktex\bin and put them back in \texmf\context\perltk (where I think
they really belong) and voila! The tuo file is now loaded and I have my
Table of Contents in my document. Hans, I hope you will comment on these
musing by a non guru so that Christian can make a more stable Context
installation as part of the general Miktex distribution. Can you explain
why Miktex failed to find texutil. Does texutil have to be in the same
directory as texexec.pl?

Finally, with the original Miktex arrangement, there was no mention of any
tuo file in the log file and no TOC. After moving texexec.ini and
texexec.pl to \texmf\Context\perltk, the inclusion of the tuo files was
clearly evidenced in the log file and I now have my TOC.

I await the recommendations of our two gurus. Also, what do we think about
these settings in texexec.ini?

% MikTeX users probably have to set up some paths too.

for  miktex  set
UsedInterfaces    to  en,nl,de,uk
for  miktex  set  UserInterface     to
en
for  miktex  set  TeXExecutable     to  pdfetex
for  miktex  set
TeXVirginFlag     to  --initialize
for  miktex  set  TeXPassString     to
--alias=context
for  miktex  set  TeXBatchFlag      to
--interaction=batchmode
for  miktex  set  MpToTeXExecutable to  mptotex
for
 miktex  set  MpVirginFlag      to  --initialize
for  miktex  set
MpPassString      to  --alias=mpost
for  miktex  set  MpBatchFlag       to
--interaction=batchmode
for  miktex  set  TeXFormatFlag     to
--undump=
for  miktex  set  MpFormatFlag      to  --undump=

At the moment, these four are the ones that are being questioned on the
Context mailing list:

for  miktex  set  TeXPassString     to  --alias=context
for  miktex  set
MpPassString      to  --alias=mpost
for  miktex  set  TeXFormatFlag     to
--undump=
for  miktex  set  MpFormatFlag      to  --undump=

The last two don't work if TeXFormatPath is set in texexec.ini:

set TeXFormatPath   to f:/localtexmf/miktex/fmt