From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: Write to tuc file
Date: Sun, 7 Mar 2021 11:04:31 +0100 [thread overview]
Message-ID: <1825a79c-172b-1344-462a-abca5d22a5e1@gmx.es> (raw)
In-Reply-To: <6965c96e-5d47-26cf-07a8-d5208b7ac707@xs4all.nl>
On 3/6/21 2:35 PM, Hans Hagen wrote:
> On 3/6/2021 1:56 PM, Pablo Rodriguez wrote:
>> [...]
>> The select style could generate from start-identifier and
>> stop-identifier, the result "identifier.pdf".
> \startchapter[reference=whatever,title=foo]
> \stopchapter
> \startchapter[reference=moreover,title=oof]
> \stopchapter
>
> and --pages=whatever,moreover will give you the info you need to call
> context --extra=copy or whatever with the right arguments
Hans,
real-world needs may be complex, such as in the following sample:
\starttext
\completecontent
\dorecurse{3}
{\startpart
\edef\pn{\recurselevel}
\dorecurse{30}
{\startchapter\markpage[start-\pn.\recurselevel]
\dorecurse{\randomnumber{0}{30}}
{\input knuth\par}
\markpage[stop-\pn.\recurselevel]\stopchapter}
\stoppart}
\stoptext
This generates a document to be split in 90 individual documents. I
cannot even think in specifying them manually.
It would be very useful to have something similar to:
context --extra=select --selection=pages oeps --once --autopdf
I hope my explanation is clearer now.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2021-03-07 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 16:58 denis.maier
2021-02-27 17:22 ` Hans Hagen
2021-02-27 17:28 ` denis.maier
2021-02-27 18:26 ` Hans Hagen
2021-02-27 21:25 ` denis.maier
2021-02-28 8:07 ` denis.maier
2021-03-05 10:29 ` Hans Hagen
2021-03-05 21:38 ` denis.maier
2021-03-05 22:13 ` Hans Hagen
2021-03-06 12:56 ` Pablo Rodriguez
2021-03-06 13:35 ` Hans Hagen
2021-03-07 10:04 ` Pablo Rodriguez [this message]
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=1825a79c-172b-1344-462a-abca5d22a5e1@gmx.es \
--to=oinos@gmx.es \
--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).