From: David Arnold <dwarnold45@cox.net>
Subject: developing large numbers of MP files for inclusion in source
Date: Fri, 23 Dec 2005 16:18:21 -0800 [thread overview]
Message-ID: <2F1ECAB6-F02B-46C8-BC39-76F1B4F5AE2F@cox.net> (raw)
Hans, Taco, et al,
Our intermediate algebra text will require a large number of figures.
I have two thoughts.
1. It's really inefficient to compile the entire context source file
just to see what will happen to one figure. So, it seems that we
should probably have a library of graphs for later inclusion in the
main document. One would want to be able to compile all at once or
individually if one were just working on one file.
2. The code for many individual figures is quite long and tends to
obscure the flow of thought when included in the source. Again, if
they were coming from an external document, that would be better.
I am not looking to include the files one at a time after
development. I know how to do that. Rather, I am looking for a way to
gather all the source for figures in a file, compile all of the file,
or just one figure from the file, then somehow call that source code
into the main .tex doc during compile time.
I am open to any suggestions on how to most efficiently develop and
include figures (in Metapost, of course) in our main document.
Thanks.
next reply other threads:[~2005-12-24 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 0:18 David Arnold [this message]
2005-12-24 9:17 ` Taco Hoekwater
2005-12-24 20:10 ` David Arnold
[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=2F1ECAB6-F02B-46C8-BC39-76F1B4F5AE2F@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).