Re: Not all the way back

Re: Not all the way back

[Hans Hagen]

At 09:12 PM 8/23/2001 -0700, David Arnold wrote:
>Hans, et al,
>
>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]?

Hans

-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: Not all the way back

[David Arnold]

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

Re[2]: Not all the way back

[Giuseppe Bilotta]

Friday, August 24, 2001 David Arnold wrote:

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

I think we could reach an agreement and let texexec config files
go (or be allowed to go) in the %texmf%/miktext/config folder.
Sounds pretty sensible to me. And of course, when multiple trees
are available, the order of search should be the same as standard
MiKTeX does. Can Hans work this out with Christian?

DA> for  miktex  set  TeXPassString     to --alias=context

I really wonder if the above is needed. Can someone really please
explain what the --alias command is used for?

I also add --terminal=oem, so that accented characters display
correctly. I decided *not* to pass the --src-special string as
well because there is a "bug" (not really a bug) in MiKTeX (any
version, AFAIK), so that pdf-variants of TeX don't ignore the
--src-specials. pdfTeX, when outputting PDF, echoes "Non-PDF
special ignored!" for each non-PDF special it meets. Which is
fine. But --src-specials *should* be ignored silenty (or, even
bettern, in PDF-production mode the --src-special flag should be
ignored).

DA> for  miktex  set  MpBatchFlag       to --interaction=batchmode

IIRC, there was a bug in MiKTeX 2.0 where MetaPost *lacked* the
interaction mode flag.

--
Giuseppe "Oblomov" Bilotta

Re[2]: Not all the way back

[Hans Hagen]

At 11:18 AM 8/25/2001 +0200, Giuseppe Bilotta wrote:

>I think we could reach an agreement and let texexec config files
>go (or be allowed to go) in the %texmf%/miktext/config folder.
>Sounds pretty sensible to me. And of course, when multiple trees
>are available, the order of search should be the same as standard
>MiKTeX does. Can Hans work this out with Christian?

the best is to use a kpsewhich alike way of locating the file, so if there 
is a miktex alternative for kpsewhich, i can support that

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re[3]: Not all the way back

[Giuseppe Bilotta]

Sunday, August 26, 2001 Hans Hagen wrote:

HH> At 11:18 AM 8/25/2001 +0200, Giuseppe Bilotta wrote:

>>I think we could reach an agreement and let texexec config files
>>go (or be allowed to go) in the %texmf%/miktext/config folder.
>>Sounds pretty sensible to me. And of course, when multiple trees
>>are available, the order of search should be the same as standard
>>MiKTeX does. Can Hans work this out with Christian?

HH> the best is to use a kpsewhich alike way of locating the file, so if there 
HH> is a miktex alternative for kpsewhich, i can support that

MiKTeX has a "initexmf" that includes function for file-searching.
I *think* 2.1 *also* has kps features, but I haven't installed it
yet, so I can't say.

--
Giuseppe "Oblomov" Bilotta

Re: Not all the way back

[Hans Hagen]

At 09:44 AM 8/24/2001 -0700, David Arnold wrote:

>texfont.pl, texshow.pl, and *MOST* importantly in this case, texutil.pl.

ah, right, you got no toc because texutil was not found -) good point

>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?

This is what the TeXScriptsPath variable can be used for.

I leave it up to you where you put the pl files since this also an OS 
issue; on texlive / win32 they go into the bin path, and in linux to 
/usr/bin [often as symlink without suffix]. If you add the perltk path to 
the PATH variable, updates will be found more conveniently, otherwise you 
need to move the files manually.

so, if in miktex they go to bin, all perl script should do;

[btw, under win, i use 4dos / 4nt which supports file name associations]

>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.

btw, if you unzip the context archive, they end up in the perltk path

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

that's what i've added / changed so far

>set TeXFormatPath   to f:/localtexmf/miktex/fmt

ideally the path should not be set, but it may come in handy for testing 
purposes

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------