ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Stephan Hennig <mailing_list@arcor.de>
To: ntg-context@ntg.nl
Subject: luaTeX and on-the-fly MetaPost compilation
Date: Fri, 23 May 2008 23:28:17 +0200	[thread overview]
Message-ID: <g17cvp$qn2$1@ger.gmane.org> (raw)

Hi,

I didn't have the opportunity to touch luaTeX yet, but let me ask one
question in advance:  Since luaTeX has a built-in MetaPost interpreter,
is it possible to refer to a certain figure in a MetaPost source file
for inclusion, instead of a compiled figure?

As an example, I would like to say in a TeX document (syntax may differ)

  \includeMetaPost{foo.2}

and this should not refer to the pre-compiled file

  foo.2

but to section

  figure(2);
    ...
  endfig;

in file

  foo.mp

and compile it on-the-fly.  Would that be possible?

Rationale:  I do not want to mix TeX and MetaPost code.  Probably, I'll
stick with compiling .mp files prior to the TeX run anyway, but I'm
curious about this option.

Best regards,
Stephan Hennig

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2008-05-23 21:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 21:28 Stephan Hennig [this message]
2008-05-24  7:28 ` Taco Hoekwater
2008-05-24  7:30 ` Hans Hagen
2008-05-24 10:49   ` Stephan Hennig
2008-05-24 13:21     ` Taco Hoekwater
2008-05-24 13:25       ` Taco Hoekwater
2008-05-24 16:54     ` 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='g17cvp$qn2$1@ger.gmane.org' \
    --to=mailing_list@arcor.de \
    --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).