From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/1550 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: Odd MP/context problems Date: Mon, 17 Jan 2000 09:33:49 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <3.0.6.32.20000117093349.008c3b60@pop.wxs.nl> References: <3880F8C2.BAA4C25C@gmx.de> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: main.gmane.org 1035392372 1314 80.91.224.250 (23 Oct 2002 16:59:32 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:59:32 +0000 (UTC) Cc: NTG-ConTeXt Original-To: Tobias Burnus In-Reply-To: <3880F8C2.BAA4C25C@gmx.de> Xref: main.gmane.org gmane.comp.tex.context:1550 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:1550 At 11:46 PM 1/15/2000 +0100, Tobias Burnus wrote: >What does this `flush and process mpgraph.mp afterwards' mean? (write18 is >enabled, but mpost is >called after pdfetex is finished, if I interprete the output of `texexec test` >correct.) There are two methods: either run MP runtime or run it afterwards. In the first case, in pdf mode, there is only one mpgraph input/output file, since it is includer at once. Graphics are collected in one file which will produce many output files (graphics). Normally texexec is able to determine how to act upon it, so normally texexec will run mp for you. (That is, when you have set up texutil in the right way -) 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.nl -----------------------------------------------------------------