From: "Johannes Hüsing" <hannes@ruhrau.de>
Subject: Re: btex and etex
Date: Sun, 14 Apr 2002 08:48:54 +0200 [thread overview]
Message-ID: <20020414084854.A897@ruhrau.de> (raw)
In-Reply-To: <3.0.6.32.20000925091346.0148b140@pop.wxs.nl>
On Mon, Sep 25, 2000 at 09:13:46AM +0200, Hans Hagen wrote:
[...]
> The btex/etex method is a tricky one. In your case, mpost still tries to
> locate an mpx file.
>
Indeed, I have tried to run the following file:
----
%\setupoutput[pdftex]
\runMPgraphicstrue
\starttext
\startuseMPgraphic{location}
u := 10pt;
v := 14pt;
draw (0u, 0v);
label.top(btex Amsterdam etex, (0u, 0v));
draw (2.4u, 2v);
label.top(btex Groningen etex, (2.4u, 2v));
draw (1.2u, 0.8v);
label.top(btex Hasselt etex, (2.4u, 0.8v));
\stopuseMPgraphic
\useMPgraphic{location}
\stoptext
----
The error message on the mpost run reads:
----
This is MetaPost, Version 0.641 (Web2C 7.3.3.1)
(minimalMP-mpgraph.mp
! mpx file ended unexpectedly.
l.22
----
> Try the latest context (esp texexec) since it implements a slightly
> different cycle,
Let's see: My texexec version is 2.5. The ConTeXt version stems from
2002.03.27.
[...]
>
> How does 'mpost myfile.mp' perform? That should use the (buggy) method
> coded in texmf.cnf.
If I run mpost on the generated Metapost inclusion, I get:
----
This is MetaPost, Version 0.641 (Web2C 7.3.3.1)
(minimalMP-mpgraph.mp (/usr/local/TeX/texmf-local/metapost/context/mp-tool.mp)
(/usr/local/TeX/texmf-local/metapost/context/mp-spec.mp)
(/usr/local/TeX/texmf-local/metapost/context/mp-grph.mp)
(/usr/local/TeX/texmf-local/metapost/context/mp-page.mp)
(/usr/local/TeX/texmf-local/metapost/context/mp-core.mp)/usr/local/bin/makempx: Command failed: tex mpxerr.tex; see mpxerr.log
>> minimalMP-mpgraph.mp
>> minimalMP-mpgraph.mpx
! Unable to make mpx file.
l.91 label.top(btex
Amsterdam etex
Transcript written on minimalMP-mpgraph.log.
----
The mpxerr.tex file reads:
----
\global \loadfontfileoncetrue%
\shipout\hbox{\smash{\hbox{\hbox{% line 91 minimalMP-mpgraph.mp
Amsterdam}\vrule width1sp}}}
\shipout\hbox{\smash{\hbox{\hbox{% line 94 minimalMP-mpgraph.mp
Groningen}\vrule width1sp}}}
\shipout\hbox{\smash{\hbox{\hbox{% line 97 minimalMP-mpgraph.mp
Hasselt}\vrule width1sp}}}
\end{document}
----
and the associated log file:
----This is TeX, Version 3.14159 (Web2C 7.3.3.1) (format=tex 2002.2.24) 14 APR 2002 08:46
**mpx1091.tex
(./mpx1091.tex
! Undefined control sequence.
l.1 \global \loadfontfileoncetrue
%
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! You can't use a prefix with `\shipout'.
<to be read again>
\shipout
l.2 \shipout
\hbox{\smash{\hbox{\hbox{% line 91 minimalMP-mpgraph.mp
I'll pretend you didn't say \long or \outer or \global.
[1] [1] [1] )
Output written on mpx1091.dvi (3 pages, 352 bytes).
---
What is hppening here?
Greetings
Johannes
--
Johannes Hüsing There is something fascinating about science. One gets
hannes@ruhrau.de such wholesale returns of conjecture from such a
trifling investment of fact. Mark Twain
prev parent reply other threads:[~2002-04-14 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-24 21:21 Peter.Andree
2000-09-25 7:13 ` Hans Hagen
2002-04-14 6:48 ` Johannes Hüsing [this message]
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=20020414084854.A897@ruhrau.de \
--to=hannes@ruhrau.de \
--cc=johannes.huesing@ruhrau.de \
/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).