Re: [NTG-context] Problems with Standalone distribution

5 Apr 2006

      ...
Date: Tue, 04 Apr 2006 00:26:12 +0200
From: Hans Hagen 
Subject: Re: [NTG-context] ntg-context Digest, Vol 22, Issue 1
To: mailing list for ConTeXt users 
Message-ID: <4431A104.9000001@wxs.nl>
Content-Type: text/plain; charset=UTF-8; format=flowed
wwl@musensturm.de wrote:
...
...
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
As I said, I work with the standalone distri?
And I thought, the binaries are from fptex, right?
And if both texexec.ini's are removed:

texexec complains: 

  warning: texexec.ini not found, try 'texexec --verbose'

(the same with texexec --verbose)
...
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
upps?

texexec (without parameters)

compiles cscite.bat! Why?
...
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)
This works!

But next Problem:

pdfetex can not find pk-fonts.

I have written: 

PKFONTS = .;$TEXMF/fonts/pk//

in 'texmf.cnf'

font-file lies in

texmf-project/fonts/pk/ricoh/local/msl/msl50.pk

what else can I do?

Wolfgang

Re: [NTG-context] Problems with Standalone distribution

wwl＠musensturm.de