From: "Haseloff, Lutz" <Lutz.Haseloff@mdf.brandenburg.de>
Cc: "'ntg-context@ntg.nl'" <ntg-context@ntg.nl>
Subject: RE: Metaerror?
Date: Mon, 18 Sep 2000 12:15:38 +0200 [thread overview]
Message-ID: <0F3313EC125AD311981100105AB3A75D4DBD45@N0795.mdf.fvbb.de> (raw)
Hi Hans, Hi all,
>>mpost complains on the commandline about:
>>
>>mpost: unrecognized option ´-progname=mpost´
>This is strange. This is pretty legal web2c. Is there a non web2c mp living
>on your system?
I use miktex + pdfetex binaries from fptex on WinNT
>>immidiate write 18 is enabled and
i changed the entry in texmf.cnf so it only is valid for pdfetex.
does metapost need this entry? How it is to set for miktex?
>You files looks ok. What does texexec --verbose report?
Output by texexec --verbose :
TeXExec 2.2 - ConTeXt / PRAGMA ADE 1997-2000
locating ini file : kpsewhich not found in path
locating ini file : found by searching
reading : c:\localtexmf\tex\context\perltk\texexec.ini
setting : 'TeXShell' to 'fptex' for 'all'
setting : 'UsedInterfaces' to 'en' for 'all'
setting : 'UserInterface' to 'en' for 'all'
setting : 'TeXExecutable' to 'pdfetex' for 'all'
setting : 'MpExecutable' to 'mp' for 'all'
setting : 'MpToTeXExecutable' to 'mptotex' for 'all'
setting : 'DviToMpExecutable' to 'dvitomp' for 'all'
setting : 'DviSpecialScript' to 'dvispec' for 'all'
setting : 'MpFormat' to 'metafun' for 'all'
setting : 'TeXFormatFlag' to '&' for 'all'
setting : 'MpFormatFlag' to '&' for 'all'
setting : 'TeXFontsPath' to
'c:/texmf/fonts;c:/localtexmf/fonts;' for 'all'
setting : 'UsedInterfaces' to 'en' for 'fptex'
setting : 'UserInterface' to 'en' for 'fptex'
setting : 'TeXExecutable' to 'pdfetex' for 'fptex'
setting : 'TeXVirginFlag' to '-ini' for 'fptex'
setting : 'TeXPassString' to '-progname=context' for 'fptex'
setting : 'TeXBatchString' to '-int=batchmode' for 'fptex'
setting : 'MpVirginFlag' to '-ini' for 'fptex'
setting : 'MpPassString' to '' for 'fptex'
setting : 'MpBatchString' to '' for 'fptex'
used setting : TeXShell = fptex
used setting : SetupPath =
used setting : UserInterface = en
used setting : UsedInterfaces = en
used setting : TeXFontsPath = c:/texmf/fonts;c:/localtexmf/fonts;
used setting : MpExecutable = mp
used setting : MpToTeXExecutable = mptotex
used setting : DviToMpExecutable = dvitomp
used setting : TeXProgramPath =
used setting : TeXFormatPath =
used setting : ConTeXtPath =
used setting : TeXScriptsPath =
used setting : TeXExecutable = pdfetex
used setting : TeXVirginFlag = -ini
used setting : TeXBatchFlag = -int=batchmode
used setting : MpBatchFlag = -int=batchmode
used setting : TeXPassString = -progname=context
used setting : TeXFormatFlag = &
used setting : MpFormatFlag = &
used setting : MpVirginFlag = -ini
used setting : MpPassString =
used setting : MpFormat = metafun
used setting : FmtLanguage =
used setting : FmtBodyFont =
used setting : TcXPath =
locating fmtutil : not found in path
--help show this or more, e.g. '--help interface'
texexec.ini :
% == introduction ==
%
% This is 'texexec.ini', the file used by texexec to determine where
% to find files, what TeX to use, what flags to pass, etc. Although
% TeXexec tries to locate things itself, a little help is sometimes
% needed. One can influence texexec by setting some variables. These
% are only needed when the automatic determined settings fail.
%
% == interfacing ==
%
% UsedInterfaces nl,en the formats generated with --make
% UserInterface nl the default format used
%
% == binaries ==
%
% TeXExecutable pdfetex the TeX binary to use
% MpExecutable mpost the MetaPost binary to use
% MpToTeXExecutable mpto the MetaPost to TeX converter
% DviToMpExecutable dvitomp the DVI to MetaPost converter
%
% == Scripts ==
%
% DviSpecialScript dvispec the DVI special filter script
%
% == flags ==
%
% TeXFormatFlag & the format introducer
% TeXVirginFlag -ini the format generation switch
%
% == paths ==
%
% TeXFormatPath texmf/... fmt files
% ConTeXtPath texmf/tex/context/base sources
% SetupPath texmf/tex/base/user cont-sys/usr file
% TeXScriptsPath texmf/context/perltk scripts
% TeXFontsPath texmf font files
%
% == the main shell setting ==
%
% As shown below, one can define his/her own sections. We default to
% the teTeX/fpTeX web2c based settings.
%set TeXShell to tetex
set TeXShell to fptex
%set TeXShell to miktex
%set TeXShell to private
% == setting up the variables ==
%
% Here are some general defaults. They can be overruled later.
set UsedInterfaces to en
set UserInterface to en
set TeXExecutable to pdfetex
set MpExecutable to mp
set MpToTeXExecutable to mptotex
set DviToMpExecutable to dvitomp
set DviSpecialScript to dvispec
set MpFormat to metafun
set TeXFormatFlag to &
set MpFormatFlag to &
set TeXFontsPath to c:/texmf/fonts;c:/localtexmf/fonts;
% For teTeX the next settings will do.
for tetex set UsedInterfaces to en,nl,de,uk
for tetex set UserInterface to en
for tetex set TeXExecutable to pdfetex
for tetex set TeXVirginFlag to -ini
for tetex set TeXPassString to -progname=context
for tetex set TeXBatchString to -int=batchmode
for tetex set MpVirginFlag to -ini
for tetex set MpPassString to -progname=mpost
for tetex set MpBatchString to -int=batchmode
% These also apply to fpTeX.
for fptex set UsedInterfaces to en
for fptex set UserInterface to en
for fptex set TeXExecutable to pdfetex
for fptex set TeXVirginFlag to -ini
for fptex set TeXPassString to -progname=context
for fptex set TeXBatchString to -int=batchmode
for fptex set MpVirginFlag to -ini
for fptex set MpPassString to
for fptex set MpBatchString to
% 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 pdftex
for miktex set TeXVirginFlag to --initialize
for miktex set TeXBatchString to
for miktex set MpVirginFlag to -ini
for miktex set MpPassString to
for miktex set MpBatchString to
% These are the settings used on some machines at PRAGMA ADE that
% don't use the texmf tree. They can serve as an example for local
% settings. Local settings should either be added to the previous
% one, or go without the 'for' directives. Consider these
% settings as an example.
for private set UsedInterfaces to en,nl
for private set UserInterface to nl
for private set ConTeXtPath to t:/sources/
for private set SetupPath to t:/perl/
for private set TeXScriptsPath to t:/perl/
% == read this too ==
%
% If this file is called 'texexec.rme', copy it to 'texexec.ini',
% check the settings above, change them according to your TeX
% distribution, and say:
%
% texexec --verbose
%
% When set up properly, you should see your local settings fly by.
% When these settings are ok, the next call should work:
%
% texexec --make
%
% and you should be able to process a file by saying
%
% texexec filename
%
% See 'mtexexec.pdf' for more information on the flags you can use with
% 'texexec'. Also make sure you have the 'texutil' script installed in
% the same path as 'texexec'.
% Experimental
%
% set TcXPath to d:/tex/texmf/web2c
% set FmtLanguage to pl
% set FmtBodyFont to plr
Greetings
Lutz
next reply other threads:[~2000-09-18 10:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-18 10:15 Haseloff, Lutz [this message]
[not found] <0F3313EC125AD311981100105AB3A75D4DBD41@N0795.mdf.fvbb.de>
2000-09-15 10:29 ` Metaerror? Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2000-09-15 9:35 Metaerror? Haseloff, Lutz
2000-09-14 10:49 Metaerror? Haseloff, Lutz
2000-09-14 12:23 ` Metaerror? Berend de Boer
2000-09-14 13:39 ` Metaerror? Tobias Burnus
2000-09-14 6:45 Metaerror? Berend de Boer
2000-09-14 8:48 ` Metaerror? Hans Hagen
2000-09-14 11:34 ` Metaerror? Berend de Boer
2000-09-14 11:37 ` Metaerror? Hans Hagen
2000-09-14 12:05 ` Metaerror? Berend de Boer
2000-09-14 12:15 ` Metaerror? Hans Hagen
2000-09-14 12:48 ` Metaerror? Berend de Boer
2000-09-14 12:40 ` Metaerror? Marc van Dongen
2000-09-14 13:20 ` Metaerror? Hans Hagen
[not found] ` <m33dj3jffv.fsf@coe.uga.edu>
2000-09-14 13:05 ` Metaerror? Berend de Boer
2000-09-14 13:23 ` Metaerror? Marc van Dongen
2000-09-14 15:28 ` Metaerror? Hans Hagen
2000-09-14 17:53 ` Metaerror? Berend de Boer
2000-09-14 18:18 ` Metaerror? Berend de Boer
2000-09-15 7:36 ` Metaerror? Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0F3313EC125AD311981100105AB3A75D4DBD45@N0795.mdf.fvbb.de \
--to=lutz.haseloff@mdf.brandenburg.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).