From: Alan Bowen <bowenalan03@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TEXpage filename
Date: Sun, 5 May 2013 08:27:36 -0400 [thread overview]
Message-ID: <CAFMOkGUNLh6sL1=z8GJAUMgg0NjWA5=oW6zjL-PUa_JQqKjcmA@mail.gmail.com> (raw)
In-Reply-To: <5A48D10C-1176-4C7C-86E1-E381A156B559@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1613 bytes --]
Wolfgang: OK—but a clarification. Yes, that will give me the individual
component files, but not with the page numbers etc that they would have
when they are compiled as part of the product. What I am interested in is
the extraction of component files during the compilation of a larger
product file—in effect, I am trying to see a way to generate offprints
without having to dismantle a PDF file (the product) manually.
I suspect now that this is actually a new thread and apologize.
Alan
On Sat, May 4, 2013 at 12:00 PM, Wolfgang Schuster <
schuster.wolfgang@gmail.com> wrote:
>
> Am 04.05.2013 um 13:50 schrieb Alan Bowen <bowenalan03@gmail.com>:
>
> > Wolfgang—
> >
> > Can this be extended so as to allow the extraction of the individual
> component files (as PDFs with their component names) when processing a
> product file?
>
> There is no need for such a feature because you can process individual
> component files without problem, you have to add only a reference to the
> project or environment at the begin of each component.
>
> Wolfgang
>
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 2473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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-05 12:27 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
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 [this message]
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='CAFMOkGUNLh6sL1=z8GJAUMgg0NjWA5=oW6zjL-PUa_JQqKjcmA@mail.gmail.com' \
--to=bowenalan03@gmail.com \
--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).