From: Olivier <billet@eurecom.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: on the fly TeX typesetting
Date: Tue, 27 May 2008 12:35:27 +0200 [thread overview]
Message-ID: <20080527103527.GA550@blackowl.org> (raw)
In-Reply-To: <483B26A2.7000508@wxs.nl>
> > I'm just wondering how TeX labels in metapost pictures are generated
> > when using mplib: if the set of pictures are all build through the
> > library which saves loading time and hd read/writes, it would be strange
> > to launch another TeX compiler.
>
> i'm not sure what you mean .. in mkiv there are no tex compilers
> launched, everything happens internally
In the case of a standalone metapost graphic, if some label requires TeX
typesetting, the metapost file is first processed by mpost, then the
need for TeX typesetting is discovered and TeX is launched to produce
the labels and they are incorporated back into the metapost figure,
right? So in the case of mplib who takes care of the label typesetting?
Does your already running instance of TeX (LuaTeX and mkiv) handles the
job of typesetting the labels? Even if this is completely disconnected
from the flow of the document currently processed?
Olivier
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-05-27 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 19:32 Olivier
2008-05-26 21:07 ` Hans Hagen
2008-05-27 10:35 ` Olivier [this message]
2008-05-27 11:52 ` Hans Hagen
2008-05-27 12:59 ` Olivier
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=20080527103527.GA550@blackowl.org \
--to=billet@eurecom.fr \
--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).