From: "Johannes Hüsing" <hannes@ruhrau.de>
Subject: "Unable to make mpx file"
Date: Sun, 7 Jul 2002 12:04:06 +0200 [thread overview]
Message-ID: <20020707100406.GA949@ruhrau.de> (raw)
Greetings,
again, I am experiencing problems with MetaPost creating files with text
included.
The following is the contents of test-mpgraph.log after processing a file
calles test.tex:
This is MetaPost, Version 0.641 (Web2C 7.3.3.1) (mem=metafun 2002.4.10) 10 APR 2002 22:25
**test-mpgraph
(test-mpgraph.mp
{randomseed:=525}
write0 = `test-mpgraph.mpo'.
>> test-mpgraph.mp
>> test-mpgraph.mpx
! Unable to make mpx file.
l.90 label(btex
Hallo wereld etex
The two files given above are one of your source files
and an auxiliary file I need to read to find out what your
btex..etex blocks mean. If you don't know why I had trouble,
try running it manually through MPto -tex, TeX, and DVItoMP.
This is what the source looks like:
\setupoutput[pdftex]
\mainlanguage[de]
\useencoding[win]
\runMPgraphicstrue
%\protectbufferstrue
% Hack, um " nicht als active character zu definieren,
% während Metapost bearbeitet wird
\appendtoks \let\handlecompoundcharacter\string \to \everyMPgraphic
\setupbodyfont
[sansserif, 18pt]
\startMPinclusions
verbatimtex
\newif\ifloadfontfileonce
etex
\stopMPinclusions
\starttext
\startuseMPgraphic{beispiel}
label(btex Hallo wereld etex, origin);
\stopuseMPgraphic
\useMPgraphic{beispiel}
\stoptext
What could be the reason?
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
next reply other threads:[~2002-07-07 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 10:04 Johannes Hüsing [this message]
2002-07-08 7:46 ` Hans Hagen
2002-07-08 19:54 ` Johannes Hüsing
2002-07-09 8:50 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2002-05-29 4:54 Johannes Hüsing
2002-05-29 7:57 ` Hans Hagen
2002-05-29 21:43 ` Johannes Hüsing
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=20020707100406.GA949@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).