From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: page ranges in \markpage
Date: Wed, 18 Jul 2018 21:38:34 +0200 [thread overview]
Message-ID: <93a3654c-bfd6-11ea-f0b8-0168115c516a@gmx.es> (raw)
In-Reply-To: <5B4F9014.7050208@gmail.com>
On 07/18/2018 09:08 PM, Wolfgang Schuster wrote:
>> Sorry, but how do I apply that with to imposed pages with \insertpages?
>>
>> I know that \filterpages is there, but I need to have the complete
>> document to print only some of the pages.
>
> You can get the number of pages of the included file with
> \getfiguredimensions.
>
> Afterwards you can use a loop where you add the markpage commands at
> the begin and end of the range, below is a simple example but it’s easy
> to write a better loop with Lua.
I see that not having a way to specify ranges in \markpages makes
complex to specify many ranges in a document.
Sorry, I understood the solution (I used a Lua loop for to impose pages
in a new PDF document some time ago), but I cannot stop thinking why the
approach to get page ranges looks so complex to me.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-07-18 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 16:19 Pablo Rodriguez
2018-07-18 17:40 ` Wolfgang Schuster
2018-07-18 18:44 ` Pablo Rodriguez
2018-07-18 19:08 ` Wolfgang Schuster
2018-07-18 19:38 ` Pablo Rodriguez [this message]
2018-07-19 19:56 ` Pablo Rodriguez
2018-07-19 22:19 ` Hans Hagen
2018-07-22 11:28 ` 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=93a3654c-bfd6-11ea-f0b8-0168115c516a@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).