From: Brooks Moses <bmoses@stanford.edu>
Subject: Re: Metapost and TeX [OT]
Date: Mon, 23 Aug 2004 23:08:33 -0700 [thread overview]
Message-ID: <20040823230833.A1639@droplet.stanford.edu> (raw)
In-Reply-To: <77347076e58b.76e58b773470@tampabay.rr.com>; from skhilji@tampabay.rr.com on Mon, Aug 23, 2004 at 10:48:42PM -0400
On Mon, Aug 23, 2004 at 10:48:42PM -0400, skhilji@tampabay.rr.com wrote:
> I don't have any experience in metapost. I would appreciate if someone would
> please answer this question without me having to do thru tutorials and
> metapost source code.
>
> I was wondering how does metapost talk to TeX? Quicky glancing through the
> metafun book, I found out that you can super-impose text typeset by
> TeX on top of a diagram. I imagine you could do the same with
> mathematical equations too.
The following is as I understand it; others can I'm sure correct any
misunderstandings:
Metapost dumps out a TeX file, consisting of any header commands
specified in the Metapost file, and whatever is between btex and etex
tags. It also puts in stuff so that what's between each pair of tags
gets put on its own page. (This is actually done with the mpto command,
rather than in Metapost itself; if you just run that, you can examine
the output to see what TeX commands it uses.)
TeX is then run on this file, creating a .dvi file.
Metapost then reads in the .dvi file, using that to create the typeset
text that appears in the output Postscript file.
- Brooks
next prev parent reply other threads:[~2004-08-24 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 2:48 skhilji
2004-08-24 3:02 ` Metapost and TeX Matthias Weber
2004-08-24 6:08 ` Brooks Moses [this message]
2004-08-24 8:18 ` Metapost and TeX [OT] Hans Hagen
2004-08-24 6:14 ` Taco Hoekwater
2004-08-24 8:21 ` 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=20040823230833.A1639@droplet.stanford.edu \
--to=bmoses@stanford.edu \
--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).