From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: "Unable to make mpx file"
Date: Wed, 29 May 2002 09:57:39 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020529095656.045a0ed8@server-1> (raw)
In-Reply-To: <20020529065435.A753@ruhrau.de>
At 06:54 AM 5/29/2002 +0200, Johannes Hüsing wrote:
>Greetings,
>
>when including TeX expressions within Metapost within a ConTeXt source,
>I get the error cited in the subject line.
>
>An examination of the mpxerr.log file reveals that the verbatimtex
>inclusions \global\loadfontfileoncetrue are not to TeX's liking.
>
>Grepping context/base for \loadfontfileoncetrue yields no result.
>Where is Metapost's TeX engine supposed to get the definition from?
>
>Sorry I have asked this question before (on Apr 14th), but not yet received
>an answer.
>grep \\ifloadfontfileonce *.tex
font-ini.tex:\newif\ifloadfontfileonce
font-ini.tex: {\ifloadfontfileonce
so, adding \newif\ifloadfontfileonce to your cont-new.tex will solve th
eproblem
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-05-29 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 4:54 Johannes Hüsing
2002-05-29 7:57 ` Hans Hagen [this message]
2002-05-29 21:43 ` Johannes Hüsing
2002-07-07 10:04 Johannes Hüsing
2002-07-08 7:46 ` Hans Hagen
2002-07-08 19:54 ` Johannes Hüsing
2002-07-09 8:50 ` 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=5.1.0.14.1.20020529095656.045a0ed8@server-1 \
--to=pragma@wxs.nl \
--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).