Installation problem

Installation problem

[Matt Gushee]

Hello, all--

I have just installed the latest (stable release of) ConTeXt on a "new"
machine [details below], but texexec is not working properly. I keep 
getting the following error:

  sh: cont-en: command not found

I have Googled for information on this problem, but the solution I found
doesn't make sense to me. In response to a previous inquiry on this
list, someone wrote:

> but the absence of cont-en that is the
> problem. Or if cont-en exists, it is not in your path or not
> executable.

But what exactly is this 'cont-en'? I have two machines with working
ConTeXt systems, and neither of them has a command with exactly that
name. So I imagine the reference is to a file named
'cont-en.<extension>'. But there is more than one such file, and none of
them seems to be a type of file that would normally be made executable
(nor are they executable on the machines where I have ConTeXt working).
Any thoughts as to what's wrong?

Oh, yes, my system is:

  Debian GNU/Linux 3.0
  teTeX 1.0.2
    * Note that teTeX comes with an old and not-properly-configured
      version of ConTeXt. I unzipped the new package over that ...
      could something left over from the old ConTeXt be causing the
      problem?

Thanks for any info.

-- 
Matt Gushee                 When a nation follows the Way,
Englewood, Colorado, USA    Horses bear manure through
mgushee@havenrock.com           its fields;
http://www.havenrock.com/   When a nation ignores the Way,
                            Horses bear soldiers through
                                its streets.
                                
                            --Lao Tzu (Peter Merel, trans.)

Re: Installation problem

[Patrick Gundlach]

Hello Matt,


> But what exactly is this 'cont-en'? 

probably a hard link to pdftex or pdfetex.

>   Debian GNU/Linux 3.0
>   teTeX 1.0.2
>     * Note that teTeX comes with an old and not-properly-configured
>       version of ConTeXt. I unzipped the new package over that ...

oh, bad thing ;-)

remove the ConTeXt stuff from there (not really necessary) and
install ConTeXt somewhere else. The directory structure has changed
so that you will get into some trouble sooner or later (kpathsea).
You need to make sure that kpathsea finds the new files before the
old ones.

See also http://levana.de/context/

Patrick

Re: Installation problem

[Thomas A. Schmitz]

cont-en.efmt is a format file that ConTeXt need to run. In order for 
this file to be built, run

texexec --make en de nl

This will create English, Dutch, and German formats (see minstall.pdf, 
p. 6-8). Depending on where and how you installed, you'll need to run 
it as root.

All best

Thomas

On Jun 21, 2004, at 10:28 AM, Matt Gushee wrote:

> Hello, all--
>
> I have just installed the latest (stable release of) ConTeXt on a "new"
> machine [details below], but texexec is not working properly. I keep
> getting the following error:
>
>   sh: cont-en: command not found
>
> I have Googled for information on this problem, but the solution I 
> found
> doesn't make sense to me. In response to a previous inquiry on this
> list, someone wrote:
>
>> but the absence of cont-en that is the
>> problem. Or if cont-en exists, it is not in your path or not
>> executable.
>
> But what exactly is this 'cont-en'? I have two machines with working
> ConTeXt systems, and neither of them has a command with exactly that
> name. So I imagine the reference is to a file named
> 'cont-en.<extension>'. But there is more than one such file, and none 
> of
> them seems to be a type of file that would normally be made executable
> (nor are they executable on the machines where I have ConTeXt working).
> Any thoughts as to what's wrong?
>
> Oh, yes, my system is:
>
>   Debian GNU/Linux 3.0
>   teTeX 1.0.2
>     * Note that teTeX comes with an old and not-properly-configured
>       version of ConTeXt. I unzipped the new package over that ...
>       could something left over from the old ConTeXt be causing the
>       problem?
>
> Thanks for any info.
>
> -- 
> Matt Gushee                 When a nation follows the Way,
> Englewood, Colorado, USA    Horses bear manure through
> mgushee@havenrock.com           its fields;
> http://www.havenrock.com/   When a nation ignores the Way,
>                             Horses bear soldiers through
>                                 its streets.
>
>                             --Lao Tzu (Peter Merel, trans.)
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>

Re: Installation problem

[Hans Hagen]

Thomas A. Schmitz wrote:

> cont-en.efmt is a format file that ConTeXt need to run. In order for 
> this file to be built, run
>
> texexec --make en de nl
>
> This will create English, Dutch, and German formats (see minstall.pdf, 
> p. 6-8). Depending on where and how you installed, you'll need to run 
> it as root.

add metafun and mptopdf; here i run:

   texexec --make --alone --all en de nl metafun mptopdf

Re: Re: Installation problem

[Matt Gushee]

On Mon, Jun 21, 2004 at 10:46:40AM +0200, Thomas A. Schmitz wrote:
> cont-en.efmt is a format file that ConTeXt need to run. In order for 
> this file to be built, run
> 
> texexec --make en de nl

Yes, I knew about that, and had already created the en and nl formats
(since I don't work with German documents at all, I don't need de, do
I?).

Just as a side note, why would the shell think the format is supposed to
be a command? That makes me wonder if there is some incorrect quoting in
the Perl script.

On Mon, Jun 21, 2004 at 10:45:37AM +0200, Patrick Gundlach wrote:
> 
> > But what exactly is this 'cont-en'? 
> 
> probably a hard link to pdftex or pdfetex.

Could be, but it's never been necessary in the past. As I mentioned, I
have two working ConTeXt installations with no such command.

> >   teTeX 1.0.2
> >     * Note that teTeX comes with an old and not-properly-configured
> >       version of ConTeXt. I unzipped the new package over that ...
> 
> oh, bad thing ;-)

Yes, I suppose so.

Well, I've deleted all the old ConTeXt directories, reinstalled the new
version, copied the *.rme files to *.ini (or whatever they are supposed
to be ... I think), regenerated the 'en', 'nl', and 'metafun' formats,
and run texhash ... I'm still getting the same error.

I also ran a diff comparing the texmf.cnf from the new installation with
one from one of my working installation. The files are identical in
everything related to ConTeXt.

So, thank you both for your quick replies, but it looks like there's
some other problem.

BTW, this is a very new release of ConTeXt--June 16, according to the 
Pragma Web site. Has anyone used this version successfully?

-- 
Matt Gushee                 When a nation follows the Way,
Englewood, Colorado, USA    Horses bear manure through
mgushee@havenrock.com           its fields;
http://www.havenrock.com/   When a nation ignores the Way,
                            Horses bear soldiers through
                                its streets.
                                
                            --Lao Tzu (Peter Merel, trans.)

Re: Installation problem

[Patrick Gundlach]

Hello,

> Well, I've deleted all the old ConTeXt directories, reinstalled the new
> version, copied the *.rme files to *.ini (or whatever they are supposed
> to be ... I think), regenerated the 'en', 'nl', and 'metafun' formats,
> and run texhash ... I'm still getting the same error.

did you update texexec and texutil?


> BTW, this is a very new release of ConTeXt--June 16, according to the 
> Pragma Web site. Has anyone used this version successfully?

The current beta is 2004.6.20 (see
http://members.ping.de:8062/context/show/HomePage ;-)

Patrick

Re: Re: Installation problem

[Matt Gushee]

On Mon, Jun 21, 2004 at 11:29:17AM +0200, Patrick Gundlach wrote:
> Hello,
> 
> > Well, I've deleted all the old ConTeXt directories, reinstalled the new
> > version, copied the *.rme files to *.ini (or whatever they are supposed
> > to be ... I think), regenerated the 'en', 'nl', and 'metafun' formats,
> > and run texhash ... I'm still getting the same error.
> 
> did you update texexec and texutil?

They are symlinks, so yes, unzipping the new archive updated them.

> > BTW, this is a very new release of ConTeXt--June 16, according to the 
> > Pragma Web site. Has anyone used this version successfully?
> 
> The current beta is 2004.6.20 (see
> http://members.ping.de:8062/context/show/HomePage ;-)

Okay, tried that, no change.

I also tried creating /usr/bin/cont-en as a symlink to pdfetex and
pdftex (not at the same time, of course). The results were, well,
different:

First, with cont-en as a link to pdftex:

| matt@crawdad:/var/tmp$ texexec ut.tex 
| 
|  TeXExec 4.3 - ConTeXt / PRAGMA ADE 1997-2004
| 
|             executable : pdfetex
|                 format : cont-en
|              inputfile : ut
|                 output : standard
|              interface : en
|           current mode : none
|                TeX run : 1
| 
| This is pdfTeX, Version 3.14159-1.00a-pretest-20011114-ojmw (Web2C 7.3.7)
| I can't find the format file `cont-en.fmt'!
| 
|            return code : 256
|               run time : 1 seconds
| 
|         total run time : 4 seconds

Can't find 'cont-en.fmt'? Well, that makes sense, doesn't it? Since, as
I understand it, ConTeXt normally uses pdfetex, which would need
cont-en.efmt. But it was worth a try.

So then I tried pdfetex:

| matt@crawdad:/var/tmp$ texexec ut.tex 
| 
|  TeXExec 4.3 - ConTeXt / PRAGMA ADE 1997-2004
| 
|             executable : pdfetex
|                 format : cont-en
|              inputfile : ut
|                 output : standard
|              interface : en
|           current mode : none
|                TeX run : 1
| 
| This is pdfeTeX, Version 3.14159-1.00a-pretest-20011114-ojmw-2.1 (Web2C 7.3.7)
| This is pdfeTeX, Version 3.14159-1.00a-pretest-20011114-ojmw-2.1 (Web2C 7.3.7)
| (/usr/share/texmf/web2c/natural.tcx)
| **
| ! End of file on the terminal... why?
| entering extended mode
| (./ut.tex
| Error: cont-en (file pdftex.cfg): cannot open config file
| 
|            return code : 65280
|               run time : 3 seconds
| 
|         total run time : 6 seconds

Hmm ... two questions here: what is the 'End of file on the terminal?'
Is that referring to natural.tcx (which comes from the ConTeXt
distribution)? And what about pdftex.cfg? Indeed, it doesn't exist. But
it doesn't exist on the machines where I have ConTeXt working, either.
So I don't know if either of the above results are meaningful.

Oh, by the way, the input file was this:

  \usetypescriptfile [type-utopia]
  \usetypescript [UtopiaFace]

  \showbodyfont [Utopia]

  \end

And yes, the typescript in question is available; both it and this test
file have worked for me on another machine.

-- 
Matt Gushee                 When a nation follows the Way,
Englewood, Colorado, USA    Horses bear manure through
mgushee@havenrock.com           its fields;
http://www.havenrock.com/   When a nation ignores the Way,
                            Horses bear soldiers through
                                its streets.
                                
                            --Lao Tzu (Peter Merel, trans.)

Re: Installation problem

[Patrick Gundlach]

Hi Matt,

I just came across the same error. I don't know why I didn't notice
before, but texexec seems to be 'broken'. Well, I don't know if it is
really broken, but it just does not to the same thing it used to. It
gives me same error as you get.

Using an old texexec works fine for me. I didn't look into this yet.

Patrick

Re: Re: Installation problem

[Hans Hagen]

Patrick Gundlach wrote:

>Hi Matt,
>
>I just came across the same error. I don't know why I didn't notice
>before, but texexec seems to be 'broken'. Well, I don't know if it is
>really broken, but it just does not to the same thing it used to. It
>gives me same error as you get.
>
>Using an old texexec works fine for me. I didn't look into this yet.
>  
>
hm, maybe some bug due to changed as a result of the new tds and binaries; i'll upload my local latest -) 

Hans 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

Re: Re: Installation problem

[Matt Gushee]

On Mon, Jun 21, 2004 at 04:57:00PM +0200, Patrick Gundlach wrote:
> 
> I just came across the same error. I don't know why I didn't notice
> before, but texexec seems to be 'broken'. Well, I don't know if it is
> really broken, but it just does not to the same thing it used to. It
> gives me same error as you get.
> 
> Using an old texexec works fine for me. I didn't look into this yet.

Ah-ha! Nice to know I'm not crazy after all.

On Mon, Jun 21, 2004 at 05:11:44PM +0200, Hans Hagen wrote:

> hm, maybe some bug due to changed as a result of the new tds and binaries; 
> i'll upload my local latest -) 

Thanks to Hans and all!

-- 
Matt Gushee                 When a nation follows the Way,
Englewood, Colorado, USA    Horses bear manure through
mgushee@havenrock.com           its fields;
http://www.havenrock.com/   When a nation ignores the Way,
                            Horses bear soldiers through
                                its streets.
                                
                            --Lao Tzu (Peter Merel, trans.)

Re: Installation problem

[Patrick Gundlach]

Hello Hans,

>>Using an old texexec works fine for me. I didn't look into this yet.
>>  
> hm, maybe some bug due to changed as a result of the new tds and
> binaries; i'll upload my local latest -) 

No change.

texexec is /opt/context/2004.6.21/bin/texexec

test$ texexec test

 TeXExec 4.3 - ConTeXt / PRAGMA ADE 1997-2004

            executable : pdfetex
                format : cont-en
             inputfile : test
                output : standard
             interface : en
          current mode : none
               TeX run : 1

warning: Could not open char translation file `cp8bit.tcx'.
This is pdfeTeX, Version 3.141592-1.11a-2.1 (Web2C 7.5.2)
kpathsea: Running mktexfmt cont-en.efmt
This is pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2C 7.5.2)
 \write18 enabled.
 %&-line parsing enabled.
 (/opt/texlive/8/texmf/web2c/cp8bit.tcx)
**
! End of file on the terminal... why?
running `pdfetex -ini   -jobname=cont-en -progname=context *cont-en.ini' ...
This is pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2C 7.5.2) (INITEX)
 \write18 enabled.
 %&-line parsing enabled.
 (/opt/texlive/8/texmf/web2c/cp8bit.tcx)
entering extended mode
(/opt/context/2004.6.21/texmf/tex/context/config/cont-en.ini{/opt/local/texmf/p
dftex/config/pdftex.cfg}

...

cp8bit is not found in the first line, but ok in the 7th. 

Do you have an idea what is going on?

Patrick

Re: Re: Installation problem

[Hans Hagen]

Patrick Gundlach wrote:

>               TeX run : 1
>
>warning: Could not open char translation file `cp8bit.tcx'.
>This is pdfeTeX, Version 3.141592-1.11a-2.1 (Web2C 7.5.2)
>kpathsea: Running mktexfmt cont-en.efmt
>This is pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2C 7.5.2)
> \write18 enabled.
> %&-line parsing enabled.
> (/opt/texlive/8/texmf/web2c/cp8bit.tcx)
>**
>! End of file on the terminal... why?
>running `pdfetex -ini   -jobname=cont-en -progname=context *cont-en.ini' ...
>This is pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2C 7.5.2) (INITEX)
> \write18 enabled.
> %&-line parsing enabled.
> (/opt/texlive/8/texmf/web2c/cp8bit.tcx)
>entering extended mode
>(/opt/context/2004.6.21/texmf/tex/context/config/cont-en.ini{/opt/local/texmf/p
>dftex/config/pdftex.cfg}
>
>...
>
>cp8bit is not found in the first line, but ok in the 7th. 
>
>Do you have an idea what is going on?
>  
>
maybe some interference with cont-en.ini; does

  texexec --make --alone

work ok?

it should not bark on the cp8bit (btw the latest version should use natural.tcx which is in the context distribution, cp8bit is flawed and not really 8 bit [straight in->out mapping is needed for instance for 
runtime xslt processign and such]; next year we can use -8bit 

(this whole 8 bit mess-up has been hauting me for years -)  


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

Re: Installation problem

[Patrick Gundlach]

Hello Hans,

> maybe some interference with cont-en.ini; does
>
>   texexec --make --alone
>
> work ok?

yes. It gives me cont-en, cont-nl,  metafun and  mptopdf  in the
current dir.

BTW: I use the current texlive (the last one shipped to members of
local tugs)

Patrick

Re: Re: Installation problem

[Hans Hagen]

Patrick Gundlach wrote:

>Hello Hans,
>
>  
>
>>maybe some interference with cont-en.ini; does
>>
>>  texexec --make --alone
>>
>>work ok?
>>    
>>
>
>yes. It gives me cont-en, cont-nl,  metafun and  mptopdf  in the
>current dir.
>
>BTW: I use the current texlive (the last one shipped to members of
>local tugs)
>  
>
hm, i always have the impression that that version is sensitive for the location of the cpx files; because i setup the texmf vars more rigurously --alone puts the formats where they belong;

future versions of tex live need more care: officially the formats will go under subpaths in web2c, but tetex will not follow that scheme; so, it's good to keep an eye on where formats finally end up; since you install fonts yourself, you may also take a look at the enc/map settings  (below); the textools script (in distribution) is able to correct the tree -) 

Hans   

--------- my setup script ---------------

# example setup file / hans hagen
#
# dos2unix setuptex
# . setuptex
# mktexlsr
# texexec --make --alone

TEXROOT=$1

if ! test -f "$TEXROOT/texmf/tex/plain/base/plain.tex" ; then
    TEXROOT="$PWD" ;
fi

if ! test -f "$TEXROOT/texmf/tex/plain/base/plain.tex" ; then
    TEXROOT="$PWD/tex" ;
fi

if ! test -f "$TEXROOT/texmf/tex/plain/base/plain.tex" ; then
    TEXROOT="/usr/local/context/tex" ;
fi

if ! test -f "$TEXROOT/texmf/tex/plain/base/plain.tex" ; then
    TEXROOT="/usr/local/tex" ;
fi

if ! test -f "$TEXROOT/texmf/tex/plain/base/plain.tex" ; then
    echo "provide a proper tex root (like /something/tex)" ;
    exit 1 ;
fi

export TEXROOT

TEXMFMAIN=$TEXROOT/texmf
TEXMFLOCAL=$TEXROOT/texmf-local
TEXMFFONTS=$TEXROOT/texmf-fonts
TEXMFEXTRA=$TEXROOT/texmf-extra
TEXMFPROJECT=$TEXROOT/texmf-project
TEXMFOS=$TEXROOT/texmf-linux
VARTEXMF=$TMP/texmf-var

export TEXMFMAIN
export TEXMFLOCAL
export TEXMFPROJECT
export TEXMFFONTS
export TEXMFEXTRA
export TEXMFOS
export VARTEXMF

CTXDEVTXPATH=
CTXDEVMPPATH=
CTXDEVMFPATH=

export CTXDEVTXPATH
export CTXDEVMPPATH
export CTXDEVMFPATH

CTXDEVPLPATH=
CTXDEVRBPATH=
CTXDEVPYPATH=
CTXDEVJVPATH=

export CTXDEVPLPATH
export CTXDEVRBPATH
export CTXDEVPYPATH
export CTXDEVJVPATH

PATH=$TEXMFOS/bin:$PATH

export PATH

# PATH=$TEXMFLOCAL\SCRIPTS\PERL\CONTEXT:$PATH
# PATH=$TEXMFLOCAL\SCRIPTS\RUBY\CONTEXT:$PATH
#
# PATH=$TEXMFLOCAL\CONTEXT\PERL:$PATH
# PATH=$TEXMFLOCAL\CONTEXT\PERLTK:$PATH
# PATH=$TEXMFLOCAL\CONTEXT\RUBY:$PATH
#
# PATH=$TEXMFPROJECT\CONTEXT\PERL:$PATH
# PATH=$TEXMFPROJECT\CONTEXT\PERLTK:$PATH
# PATH=$TEXMFPROJECT\CONTEXT\RUBY:$PATH
# PATH=$TEXMFPROJECT\CONTEXT\BIN:$PATH
#
# export PATH

# the next lines fail on dec alpha os's, so there you need
# to comment them (bug traced down by kees van marle/martin
# corrino)

HOMETEXMF=/nonexist
export HOMETEXMF

TEXMFCNF=$TEXROOT/texmf{-local,}/web2c
TEXMF='{$TEXMFOS,$TEXMFPROJECT,$TEXMFFONTS,$TEXMFLOCAL,$TEXMFEXTRA,!!$TEXMFMAIN}'
TEXMFDBS=$TEXMF

export TEXMFCNF
export TEXMF
export TEXMFDBS

TEXFORMATS=$TEXMFOS/web2c
MPMEMS=$TEXFORMATS
TEXPOOL=$TEXFORMATS
MPPOOL=$TEXFORMATS

export TEXFORMATS
export MPMEMS
export TEXPOOL
export MPPOOL

TEXINPUTS=
MPINPUTS=
MFINPUTS=

export TEXINPUTS
export MPINPUTS
export MFINPUTS

# SET EXAMPLEROOT=$VARTEXMF
# EXPORT EXAMPLEROOT

if ((test -w "$TEXMFOS/bin/texmfstart") && (! test -x "$TEXMFOS/bin/texmfstart")) ; then
    chmod 755 $TEXMFOS/bin/*
fi

------ my config file -----------

% This file loads before texmf/web2c/texmf.cnf; beware :
% the selfish auto parent can get in the way especially when
% the binaries are located elsewhere. In case of multiple
% trees, one can best set the following ones manually.

TEXMFMAIN     = $SELFAUTOPARENT/texmf
TEXMFLOCAL    = $SELFAUTOPARENT/texmf-local
TEXMFFONTS    = $SELFAUTOPARENT/texmf-fonts
TEXMFEXTRA    = $SELFAUTOPARENT/texmf-extra
TEXMFPROJECTS = $SELFAUTOPARENT/texmf-projects
VARTEXMF      = $SELFAUTOPARENT/texmf-var
HOMETEXMF     = /nonexist
TEXMF         = {$TEXMFPROJECT,$TEXMFFONTS,$TEXMFLOCAL,$TEXMFEXTRA,!!$TEXMFMAIN}
SYSTEXMF      = $TEXMF

TEXMFCNF      = .;$TEXMF/texmf{-local,}/web2c
TEXMFDBS      = $TEXMF;$VARTEXFONTS

VARTEXFONTS   = $TEMPFONTPATH/varfonts

% In the case of an multi-os setup, this one can be set
% by the environment.

TEXFORMATS    = .;$TEXMF/web2c
MFBASES       = .;$TEXFORMATS
MPMEMS        = .;$TEXFORMATS
TEXPOOL       = .;$TEXFORMATS
MFPOOL        = .;$TEXFORMATS
MPPOOL        = .;$TEXFORMATS

WEB2C         = $TEXMF/web2c

% fonts

TEXPSHEADERS  = .;$TEXMF/{fonts/{enc,map,type1,truetype},dvips,pdftex,tex}//;$TEXMF/{etex,tex,pdftex,dvips,fonts/type1}//
TEXFONTMAPS   = .;$TEXMF/{fonts/map//,fontname};$TEXMF/{pdftex,dvips}/config;$TEXMF/{pdftex,dvips}//

VFFONTS       =	.;$TEXMF/fonts/vf//
TFMFONTS      =	.;{$TEXMF/fonts,$VARTEXFONTS}/tfm//

T1FONTS       =	.;$TEXMF/fonts/{type1,pfb}//;$TEXMF/fonts/misc/hbf//
AFMFONTS      =	.;$TEXMF/fonts/afm//
LIGFILES      =	.;$TEXMF/fonts/lig//
TTFONTS       =	.;$TEXMF/fonts/{truetype,ttf}//
TTF2TFMINPUTS =	.;$TEXMF/ttf2pk//
T42FONTS      =	.;$TEXMF/fonts/type42//
MISCFONTS     =	.;$TEXMF/fonts/misc//
ENCFONTS      = .;$TEXMF/{fonts/enc,dvips}//
CMAPFONTS     = .;$TEXMF/fonts/cmap//
SFDFONTS      = .;$TEXMF/fonts/sfd//
OPENTYPEFONTS = .;$TEXMF/fonts/opentype//

OFMFONTS      =	.;{$TEXMF/fonts,$VARTEXFONTS}/{ofm,tfm}//;$TFMFONTS
OPLFONTS      =	.;{$TEXMF/fonts,$VARTEXFONTS}/opl//
OVFFONTS      =	.;{$TEXMF/fonts,$VARTEXFONTS}/ovf//
OVPFONTS      =	.;{$TEXMF/fonts,$VARTEXFONTS}/ovp//
OTPINPUTS     =	.;$TEXMF/omega/otp//
OCPINPUTS     =	.;$TEXMF/omega/ocp//

% configurations

$CTXDEVTXPATH=rubish
$CTXDEVMPPATH=rubish
$CTXDEVMFPATH=rubish

TEXINPUTS.context = .;$CTXDEVTXPATH//;$TEXMF/{pdftex,pdfetex,etex,omega,tex}/{context,plain,generic,}//
MPINPUTS          = .;$CTXDEVMPPATH//;$TEXMF/metapost//
MFINPUTS          = .;$CTXDEVMFPATH//;$TEXMF/metafont//;{$TEXMF/fonts,$VARTEXFONTS}/source//

TEXCONFIG     =	.;$TEXMF/{fonts/map,dvips,pdftex}//
PDFTEXCONFIG  = .;$TEXMF/pdftex/{$progname,}//
DVIPDFMINPUTS =	.;$TEXMF/{dvipdfm,{dvips,fonts/{map,enc}/{dvips,}}}//

% for the moment we keep these and also keep a backward compatible path spec

$CTXDEVPLPATH=rubish
$CTXDEVPYPATH=rubish
$CTXDEVRBPATH=rubish
$CTXDEVJVPATH=rubish

PERLINPUTS   = .;$CTXDEVPLPATH//;$TEXMF/scripts/context/perl//;$TEXMF/{context/perl,context/perltk,perl,perltk}//
PYTHONINPUTS = .;$CTXDEVPYPATH//;$TEXMF/scripts/context/python//;$TEXMF/{context/python,python}//
RUBYINPUTS   = .;$CTXDEVRBPATH//;$TEXMF/scripts/context/ruby//;$TEXMF/{context/ruby,ruby}//
JAVAINPUTS   = .;$CTXDEVJVPATH//;$TEXMF/scripts/context/java//;$TEXMF/{context/java,java}//

TEXMFSCRIPTS = .;$CTXDEVRBPATH//;$CTXDEVPLPATH//;$TEXMF/scripts/context//;$TEXMF/scripts//

% features

shell_escape            = t
%openout_any             = a
openout_any             = p
openin_any              = a
parse_first_line        = f
allow_multiple_suffixes = f

% auto generation

MKTEXTEX = 0
MKTEXPK  = 0
MKTEXMF  = 0
MKTEXTFM = 0
MKOCP    = 0
MKOFM    = 0

% metapost

MPXCOMMAND = texexec --batch --once --nomp --mptex
TEX        = texexec --batch --once --nomp

% These values are about the same as in the main
% configuration file (dest_names_size added).

buf_size.context         =  200000 % needed for omega bug
extra_mem_bot.context    = 2000000
extra_mem_top.context    = 4000000
font_max.context         =    2000
font_mem_size.context    = 1000000
hash_extra.context       =   50000
main_memory.context      = 1500000
max_strings.context      =  100000
nest_size.context        =     500
obj_tab_size.context     =  300000
dest_names_size.context  =  300000
param_size.context       =    5000
pool_free.context        =   47500
pool_size.context        = 1250000
save_size.context        =   50000
stack_size.context       =    5000
string_vacancies.context =   90000
trie_size.context        =  250000

main_memory.mpost        = 3000000
pool_size.mpost          = 3000000
path_size.mpost          =   10000

main_memory.metafun      = 3000000
pool_size.metafun        = 3000000
path_size.metafun        =   10000

buf_size                 =  100000

mp_buf_size              =   30000
mf_buf_size              =   30000
mpost_buf_size           =   30000

max_print_line.mpost     =     250
max_print_line.metafun   =     250

extra_mem_top.mptopdf    = 1000000
extra_mem_bot.mptopdf    = 1000000

ocp_buf_size             =  500000
ocp_stack_size           =   10000
ocp_list_size            =    1000


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

Re: Installation problem

[Patrick Gundlach]

Hello Hans and Matt,


here is my solution:

in texexec.ini change

set  TeXFormatFlag      to  &

into:

set  TeXFormatFlag      to  

(empty)


and run texexec like:

texexec --tex=pdfetex file.tex


this is because texexec checks 

if ( $TeXFormatFlag eq "" ) {
    if ($TeXProgram =~ /(etex|pdfetex)/) {
        $TeXFormatFlag = "-efmt=" ; # >=2004 -fmt=
    } elsif ($TeXProgram =~ /(eomega)/) {
        $TeXFormatFlag = "-eoft=" ; # >=2004 obsolete
    } elsif ($TeXProgram =~ /(aleph)/) {
        $TeXFormatFlag = "-fmt=" ;
    } else {
        $TeXFormatFlag = "-fmt=" ;
    }
}


and $TeXProgram is not set to $TeXExecutable (why the two different vars?)


Patrick

Re: Re: Installation problem

[Hans Hagen]

Patrick Gundlach wrote:

> <>here is my solution:
>
> in texexec.ini change
>
> set TeXFormatFlag to &
>
> into:
> set TeXFormatFlag to
>
> (empty)
>
>
> and run texexec like:
>
> texexec --tex=pdfetex file.tex
>
>
> this is because texexec checks
>
> if ( $TeXFormatFlag eq "" ) {
> if ($TeXProgram =~ /(etex|pdfetex)/) {
> $TeXFormatFlag = "-efmt=" ; # >=2004 -fmt=
> } elsif ($TeXProgram =~ /(eomega)/) {
> $TeXFormatFlag = "-eoft=" ; # >=2004 obsolete
> } elsif ($TeXProgram =~ /(aleph)/) {
> $TeXFormatFlag = "-fmt=" ;
> } else {
> $TeXFormatFlag = "-fmt=" ;
> }
> }


indeed, the texexec.rme file is changed accordingly; i needed that 
change because & is giving to much problems in nested calls; also, next 
year there will be changes again because from now on web2c formats will 
be fmt, like

  web2c/pdfetex/cont-en.fmt

instead of

  web2c/cont-en.efmt

(currently both -efmt and -fmt are handled by the latest pdfetex) ; i 
didn't check miktex yet

> <>and $TeXProgram is not set to $TeXExecutable (why the two different 
> vars?)

dunno, must have a look

Hans

Re: Installation problem

[Patrick Gundlach]

Matt Gushee <mgushee@havenrock.com> writes:

>> texexec --make en de nl
>
> Yes, I knew about that, and had already created the en and nl formats
> (since I don't work with German documents at all, I don't need de, do
> I?).

No, you don't need de. Even when you want to typeset german
documents, you don't need de. (Trust me, I typeset german documents,
but never create the german format file :)

Patrick
-- 
texshow-web:  http://members.ping.de:8061
ConTeXt wiki: http://members.ping.de:8062

Re: Re: Installation Problem

[h h extern]

David Arnold wrote:

> Patrick,
> 
> Ah! I am looking in cont-tmf.zip and I see that there no longer is a
> /context/perltk.

oeps, i need to fix that; the problem is that we're in a transition from 
old TDS to new TDS (tex directory structure), so either manuals are 
behind or ahead (and since some changes are not downward compatible this 
poses some timing)

> Looks like the installation directions haven't caught up with the release.

indeed; i'll start doing that once i have the new web site up and 
running (i'm still reorganizing some things)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

Re:Installation Problem

[David Arnold]

Larry,

Thanks. But no occurrence of gebied in my texexec.pl.

>I got a similar error message on my linux box.  The solution was to
>replace a single occurrence of the instruction "\c!gebied" in texexec.pl
>with "\c!directory".  I suspect this is an errant piece of Dutch
>language code that escaped the recent tranlation to low-level English.
>
>-- 
>Larry Stamm
>
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>

Re: Re: Installation Problem

[David Arnold]

Patrick,

Ah! I am looking in cont-tmf.zip and I see that there no longer is a
/context/perltk.

Unfortunately, the installation directions minstall.pdf in cont-tmf.zip
says there is. Indeed, see pages 2 and 5, where it says to put
\miktex\context\perltk on your path.

Looks like the installation directions haven't caught up with the release.

I'm going to try deleting the original context tree, unzipping again, then
putting /miktex/scripts/context/perl on the path and I'll report what happens.

At 11:55 AM 10/16/04 +0200, you wrote:
>Hi David,
>
>
>does 
>http://archive.contextgarden.net/message/20041011.122555.3827e19a.html
>
>help?
>
>
>Patrick
>-- 
>ConTeXt wiki: http://contextgarden.net
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>

Re:Installation Problem

[Larry Stamm]

 David Arnold <darnold@northcoast.com> writes:

    > All, Got the latest cont-tfm.zip from:

    > http://www.pragma-ade.com/context/current/cont-tmf.zip

    > Extracted with WinZip on my Win95 machine running Miktex.

<snip installation steps..>

    > Got this error:

    > This is pdfeTeX, Version 3.141592-1.10b-2.1 (MiKTeX 2.3) entering
    > extended mode (junk.tex{pdftex.cfg}

    > ConTeXt ver: 2004.10.07 fmt: 2004.10.15 int: english mes: english

    > systems : pdfTeX version 110 -> please update

    > systems : eTeX version 201 -> too old (bugs)

    > language : language en is active <protectionstate 0> system :
    > cont-new loaded (F:\miktex\tex\context\base\cont-new.tex systems :
    > beware: some patches loaded from cont-new.tex!  color : palette
    > rollover is available system (E-TEX) : [line 966] system (E-TEX) :
    > [line 1021] ) system : cont-old loaded
    > (F:\miktex\tex\context\base\cont-old.tex loading : Context Old
    > Macros ) system : cont-fil loaded
    > (F:\miktex\tex\context\base\cont-fil.tex loading : Context File
    > Synonyms ) bodyfont : 12pt rm is loaded language : patterns
    > en->default:default->1->2:2
    uk-> default:default->2->2
    > :2 de->texnansi:texnansi->3->2:2 de->ec:ec->4->2:2
    fr-> texnansi:texnansi->5->2:
    > 2 fr->ec:ec->6->2:2 es->default:default->7->2:2
    it-> texnansi:texnansi->8->2:2 i
    t-> ec:ec->9->2:2 nl->texnansi:texnansi->10->2:2 nl->ec:ec->11->2:2
    t-> loaded
    > specials : tex,postscript,rokicki loaded system : junk.top loaded
    > (./junk.top ! Undefined control sequence.  <argument> \c!gebied
    > ={C:/} \xprocesscommaitem #1,#2->\if ,#1 ,\@EA \xprocesscommaitem
    > \else \if ]#1\@EAE...

    > \xdogetparameters #1]->\xprocesscommaitem #1,] ,\@relax@
    > \dosetupsystem [#1]->\getparameters [\??sv ][#1] \setuprandomize
    > [\@@svrandom...  l.3 ...ost
    > --undump=}\setupsystem[\c!gebied={C:/}]

    > ?

    > Any ideas?

I got a similar error message on my linux box.  The solution was to
replace a single occurrence of the instruction "\c!gebied" in texexec.pl
with "\c!directory".  I suspect this is an errant piece of Dutch
language code that escaped the recent tranlation to low-level English.

-- 
Larry Stamm