From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TEXpage filename
Date: Wed, 1 May 2013 23:11:42 +0200 [thread overview]
Message-ID: <20130501231142.6c1c8f28@iram-hb-003386.extra.cea.fr> (raw)
In-Reply-To: <CAF=dkzx3Qnc5d6a7U5gLqNii7SJ9j8Lww31=-xR-+1uWk+RzGw@mail.gmail.com>
On Wed, 1 May 2013 16:16:07 +0200
Sietse Brouwer <sbbrouwer@gmail.com> wrote:
> Alan wrote:
> > In the production of (scientific) articles for
> > journal submissions, one is often expected to
> > supply the figures as separate files.
> >
> > One workflow can be through the use of \startTEXpage\stopTEXpage
> > followed by an external extraction of single pdf pages to separate
> > files.
>
> It might be easier to place the figure code in a separate file
This is one workflow that I classically use: as separate product in a
project. However, I was exploring how to include the figure (or table,
etc.) code in the standard product file with separate TEXpage output
streams.
Alan
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-05-01 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 10:16 Alan BRASLAU
2013-05-01 14:16 ` Sietse Brouwer
2013-05-01 21:11 ` Alan BRASLAU [this message]
2013-05-01 21:02 ` Wolfgang Schuster
2013-05-02 6:44 ` Wolfgang Schuster
2013-05-04 11:50 ` Alan Bowen
2013-05-04 16:00 ` Wolfgang Schuster
2013-05-05 12:27 ` Alan Bowen
2013-05-05 12:39 ` Thomas A. Schmitz
2013-05-08 12:00 ` Alan Bowen
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=20130501231142.6c1c8f28@iram-hb-003386.extra.cea.fr \
--to=alan.braslau@cea.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).