Hi Hans, I still have trouble with the metafun mem when using the newtexexec. Missing specials, to be precise, because the runtime mpost reads different values from texmf.cnf from the ini mpost. The root of the problem is that texexec --make metafun runs the following command: mpost -progname=metafun --ini -translate-file=natural.tcx metafun But texexec talk runs: mpost -progname=mpost -mem=metafun -translate-file=natural.tcx \ talk-mpgraph.mp (I have separate settings in texmf.cnf for mpost, metafun, and mpplain). Cheers, taco
Taco Hoekwater wrote:
Hi Hans,
I still have trouble with the metafun mem when using the newtexexec. Missing specials, to be precise, because the runtime mpost reads different values from texmf.cnf from the ini mpost.
The root of the problem is that
texexec --make metafun
runs the following command:
mpost -progname=metafun --ini -translate-file=natural.tcx metafun
But
texexec talk
runs:
mpost -progname=mpost -mem=metafun -translate-file=natural.tcx \ talk-mpgraph.mp
(I have separate settings in texmf.cnf for mpost, metafun, and mpplain).
so we need the commented version: # command = [quoted(mpsengine),prognameflag(progname),formatflag(mpsengine,mpsformat),tcxflag,runoptions(mpsengine),filename,mpsprocextras(mpsformat)].join(' ') command = [quoted(mpsengine),"-progname=mpost",formatflag(mpsengine,mpsformat),tcxflag,runoptions(mpsengine),mpname,mpsprocextras(mpsformat)].join(' ') what happens if mp is run and an unknown progname is used (imagine texmf.cnf files without metafun entry) and, what doe sprogname default to in mp, the format? if so, we can leave out the progname for mp 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 -----------------------------------------------------------------
participants (2)
-
Hans Hagen
-
Taco Hoekwater