From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: btex etex trouble
Date: Fri, 13 Jul 2001 22:42:46 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010713223918.02e4de18@server-1> (raw)
In-Reply-To: <5.1.0.14.0.20010712155044.00a9b688@public.uni-hamburg.de>
At 02:48 PM 7/12/2001 +0000, Eckhart Guthöhrlein wrote:
>I have some questions/remarks on inclusion of mp graphics with btex/etex.
>Sorry if I overlooked something in the docs, I'm rather exhausted now...
>
>Is there a way to tell context to write mpgraph.mp files suitable for plain
>tex, not for context? I got the following error message
% output=pdftex
\starttext
\startMPpage
metapost code
\stopMPpage
\stoptext
This is nearly plain, and context understands most plain tex commands,
>by tex when called by mp. I managed to instruct mp to call context instead
>of plain tex, so it works now, but plain tex would be enough for me (simple
>text, cm fonts) and considerably faster. Inspection of mpgraph.mp showe
The latest version of context is (up to twice) as fast (depending on the
task).
>graphictextformat := "context" ;
>graphictextdirective "\global \loadfontdefinitionfileoncetrue " ;
>
>Can this be changed? Or something else? Or is it impossible / undesirable
>to use plain tex for some reasons I don't see?
Not so much impossible, more a lack of need and time.
It can be compiled using context and further processed by dvitomp, no
>problem, but where does \end{document} come from? Looks like latex.
This is generated by the metapost related tools: \end is also valid plain
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
-------------------------------------------------------------------------
prev parent reply other threads:[~2001-07-13 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 14:48 Eckhart Guthöhrlein
2001-07-13 20:42 ` Hans Hagen [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=5.1.0.14.1.20010713223918.02e4de18@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).