From: Hans Hagen <j.hagen@xs4all.nl>
To: denis.maier@ub.unibe.ch, ntg-context@ntg.nl
Subject: Re: Write to tuc file
Date: Fri, 5 Mar 2021 11:29:20 +0100 [thread overview]
Message-ID: <108e97a3-5125-adf6-ed60-7eed7189fc31@xs4all.nl> (raw)
In-Reply-To: <a7116b2d1a104a9c90aad92744768543@ub.unibe.ch>
On 2/27/2021 6:28 PM, denis.maier@ub.unibe.ch wrote:
> It's a book that will be published in two volumes, continually paginated.
> In the end I need two pdf files, but I thought it might be easier to treat them as one volume and just split the files with some external tool afterwards.
>
> I could also treat them as two individual books, but then I'd have to get the last page number of volume 1 in volume 2.
In the early days of context (more than 2 decades ago) we had a printer
where we could inject from different trays and that is why we have a
feature in context to mark pages (so that directives for printers could
be inserted). This feature survived / evolved into marked pages.
You can do this (oeps.tex):
\starttext
\chapter[one]{One}
\markpage[first] test \page test \page
\markpage[second] test \page
\chapter[two]{Two}
test \page
\markpage[fourth] test
\page
% \doifelsemarkedpage{second}{YES}{NO}
% \doifelsemarkedpage{fourth}{YES}{NO}
% \page
% \doifelsemarkedpage{second}{YES}{NO}
% \doifelsemarkedpage{fourth}{YES}{NO}
\stoptext
So, I was wondering if we can expose that differently.
>context --pages oeps
mtx-context | page : 0001 first
mtx-context | page : 0003 second
mtx-context | page : 0005 fourth
>context --pages --page=second oeps
mtx-context | page : 0003 second
>context --pages --page=second,fourth oeps
mtx-context | page : 0003 second
mtx-context | page : 0005 fourth
But, as you're talking chapters, a variants (with less overhead) is:
>context --pages --list=one,two oeps
mtx-context | list : 0001 one
mtx-context | list : 0004 two
Which of course assumes that you have a reference for the chapters.
This --pages feature is in the latest upload.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-03-05 10:29 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 [this message]
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
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=108e97a3-5125-adf6-ed60-7eed7189fc31@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=denis.maier@ub.unibe.ch \
--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).