Re: [NTG-context] ntg-context Digest, Vol 22, Issue 1

2006-04-03 Thread wwl
 ok! I have modified the batch-files.
 
 Next Problems: 
 
 texexec.ini is not found in 'context\config'
 I copyed it in 'scripts\context\perl'
 now it is found. 

Is this normal? Or is this a symptome of the problem I am looking 
for?
 
 'texexec --verbose' tries to compile all the files in the aktuel 
 path.
 
 but
 
 'texmfstart texexec.pl --verbose' works ok.
 
 same with
 
 'texexec --make --all' doesn't work
 
 but 
 
 'texmfstart texexec.pl --make --all' works!
 
 formatfiles will generatet under '.\pdfetex' relativ to the aktual
 path.

I have found TWO different files 'texmf.cnf'.
One in 'tex\texmf\web2c' the other in 'tex\texmf-local\web2c'.
Meight this be an Problem? Which of them is the right one?

I have NOT found any file 'pdftex.cfg'.
Ist this normal?

In 'texmf.cnf' are some pathes written with '/' and '\' mixed.
Should this be korrekted.

Wolfgang

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] ntg-context Digest, Vol 22, Issue 1

2006-04-03 Thread Hans Hagen
[EMAIL PROTECTED] wrote:
 ok! I have modified the batch-files.

 Next Problems: 

 texexec.ini is not found in 'context\config'
 I copyed it in 'scripts\context\perl'
 now it is found. 
 

 Is this normal? Or is this a symptome of the problem I am looking 
 for?
   
it depends on what system you use; the settinsg default to 
tetex/fptex/gwtex so in that case no ini is needed

newtexexec.rb (which will replace texexec.pl) has no ini file but uses 
some heuristics to determine what environment it runs in
  
   
 'texexec --verbose' tries to compile all the files in the aktuel 
 path.

 but

 'texmfstart texexec.pl --verbose' works ok.

 same with

 'texexec --make --all' doesn't work

 but 

 'texmfstart texexec.pl --make --all' works!
 
good

on windows: you need to associate the pl suffix to perl
on linux you need to make  texexec into a script (suffixless)

on both you can best use texmfstart to launch the scripts since that's 
upward compatible (and in some respects this call is more clever); if 
needef you can create stubs with texmfstart (see manual)

 formatfiles will generatet under '.\pdfetex' relativ to the aktual
 path.
 

 I have found TWO different files 'texmf.cnf'.
 One in 'tex\texmf\web2c' the other in 'tex\texmf-local\web2c'.
 Meight this be an Problem? Which of them is the right one?
   
normally the local one will be loaded first and variables set in the 
environment are ignored
 I have NOT found any file 'pdftex.cfg'.
 Ist this normal?
   
yes, that file is gone in recent pdftex's (best not use an old pdfetex 
with a new tree
 In 'texmf.cnf' are some pathes written with '/' and '\' mixed.
 Should this be korrekted.
   
normally no problem since kpse normalizes paths 
 
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
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context