ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gerben Wierda <gerben.wierda@rna.nl>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: startMPpage..stopMPpage written to a separate PDF?
Date: Sun, 5 Apr 2020 12:27:05 +0200	[thread overview]
Message-ID: <4E6F4C4E-C277-401C-A4D4-2045B09837AA@rna.nl> (raw)
In-Reply-To: <e122852e-6e4e-f665-9213-a0b7d73c4a1c@xs4all.nl>



> On 5 Apr 2020, at 11:34, Hans Hagen <j.hagen@xs4all.nl> wrote:
> 
> On 4/5/2020 12:29 AM, Gerben Wierda wrote:
>> I have a series of startMPpage—stopMPpage pairs (with MP code inbetween). These now become separate pages in a single PDF. But I need them to become separate PDF’s each during my ConTeXt run, with a name of my own choosing. Is this possible? I guess this will be problematic, but one can hope (maybe some very low level TeX trickery)...
> no (i would probably cook up something but it's not worth the trouble and it would add lots of ugly code deep down) but

Yes, I was thinking about some low level open/writeout stuff in TeX but was scared to try.

Still, a \startMPfile{pdffilename}..\stopMPfile (instead of page) would have been great...

> you can use for instance mutool etc to split pdf’s

I can’t do that simply because it would mean lots and lots of manual work (including typing long names every time) each time I automatically produce the PDFs. I am talking hundreds of views generated anew every time and they all need to end up in a separate file. I need some sort of automatic flow. It’s OK if the PDF with all the pages is an intermediate and use a tool to split this into separate files with separate file names (so an additional step in the workflow) but I would have to create th eextraction script automatically during the ConTeXt run. 

Alternatively, I could have a step before this to turn the input XML into many separate XMLs and have many ConTeXt runs. Probably that is the best way to do it. Each generated XML would have all of the original XML except it would only have one ‘view’ in it and the rest removed.

> 
> 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
___________________________________________________________________________________

  reply	other threads:[~2020-04-05 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 22:29 Gerben Wierda
2020-04-05  9:34 ` Hans Hagen
2020-04-05 10:27   ` Gerben Wierda [this message]
2020-04-06  7:42     ` Taco Hoekwater
2020-04-06 12:49     ` Wolfgang Schuster

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=4E6F4C4E-C277-401C-A4D4-2045B09837AA@rna.nl \
    --to=gerben.wierda@rna.nl \
    --cc=j.hagen@xs4all.nl \
    --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).