From: David Arnold <dwarnold45@cox.net>
Subject: Re: developing large numbers of MP files for inclusion in source
Date: Sat, 24 Dec 2005 12:10:57 -0800 [thread overview]
Message-ID: <1ED3A921-3CB2-4201-9D57-4F37A5BBC23B@cox.net> (raw)
In-Reply-To: <43AD1225.9030509@elvenkind.com>
Do you have one metapost file with many figures in it? Is it possible
to just compile for the figurein that file that you want? Is there
a command that will compile then show the result?
On Dec 24, 2005, at 1:17 AM, Taco Hoekwater wrote:
> David Arnold wrote:
>> I am open to any suggestions on how to most efficiently develop
>> and include figures (in Metapost, of course) in our main document.
>
> Well, if you do not depend on metafun -- context interaction, then
> I would just create a metapost input file per chapter, and compile
> it with mpost off-line (it they are complicated, even pre-run mptopdf
> to save time during the inclusion phase).
>
> Then include the image in the document just like I would a 'normal'
> external figure or even table). I have a separate per-chapter
> directory
> for that to avoid clutter. It is not most high-tech solution, but I
> find it quite workable.
>
> So, my tree structure usually looks like this:
>
> ./book.tex
> ./style.tex
> ./chapter1.tex % those are components
> ./chapter2.tex
> ...
> ./chapter1/figure.mp
> ./chapter1/figure.1
> ./chapter1/figure.2
> ./chapter1/whatever.png
> ./chapter1/table-1.tex
>
> Cheers,
>
> Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2005-12-24 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 0:18 David Arnold
2005-12-24 9:17 ` Taco Hoekwater
2005-12-24 20:10 ` David Arnold [this message]
[not found] ` <6faad9f00512241617n4a2102c6mcdde847afc67ea48@mail.gmail.com>
2005-12-25 0:25 ` David Arnold
2005-12-25 7:50 ` Taco Hoekwater
2005-12-24 15:05 ` Henning Hraban Ramm
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=1ED3A921-3CB2-4201-9D57-4F37A5BBC23B@cox.net \
--to=dwarnold45@cox.net \
--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).