From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Disable reuse of figures
Date: Sat, 19 Feb 2022 11:26:56 +0100 [thread overview]
Message-ID: <4ef10093-262f-86cb-395e-fd8650fc37e5@xs4all.nl> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2202190110440.469458@nqv-guvaxcnq>
On 2/19/2022 7:30 AM, Aditya Mahajan via ntg-context wrote:
> Hi,
>
> This is related to a bug report for the filter module:
> https://github.com/adityam/filter/issues/60
>
> Normally, when the same figure is included twice, context only includes the figure once and refers to the included figure the second time. The option `object=no` to externalfigure is supposed to prevent that, but it doesn't work. For example, consider the following example the bug-report uses graphviz as the external program, but I have changed that to context to keep things self contained)
>
> \usemodule[filter]
>
> \defineexternalfilter
> [graphviz]
> [
> filter=context --purge,
> output=\externalfilterbasefile.pdf,
> readcommand=\ReadPDF,
> ]
>
> \def\ReadPDF#1%
> {\externalfigure[#1][object=no]}
>
> \starttext
>
> Circle:
> \startgraphviz
> \startMPpage
> draw fullcircle scaled 1cm;
> \stopMPpage
> \stopgraphviz
>
> Square:
> \startgraphviz
> \startMPpage
> draw fullsquare scaled 1cm;
> \stopMPpage
> \stopgraphviz
>
> \stoptext
>
> Behind the scenes, the first \startgraphviz ... \stopgraphviz environment writes the content to an external file (\jobname-temp-graphviz.tmp), runs `context --purge \jobname-temp-graphviz.tmp`, which creates `\jobname-temp-graphviz.pdf`. The `\ReadPDF` macro then includees the file (with object=no).
>
> At the next \startgraphviz .. \stopgraphviz, the same process is repeated. The `\jobname-temp-graphviz.pdf` file is overwritten and the new file should have been included. But it is not. The output contains the first image twice.
>
> I thought that object=no should have prevented the reuse. In fact, if I compile the file with luatex, I get an error message:
>
> ! error: (pdf inclusion): file has changed '12-two-outputs-temp-graphviz.pdf'
> mtx-context | fatal error: return code: 256
>
> Any idea why object=no is not working?
the pdf file is kept open, for various reasons:
- performance
- the might be different pages to fetch
- analysis happens when the image is placed, inclusion happens later
so you try to reopen an already open file (which has not been completely
processed)
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:[~2022-02-19 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 6:30 Aditya Mahajan via ntg-context
2022-02-19 10:26 ` Hans Hagen via ntg-context [this message]
2022-02-21 9:47 ` Aditya Mahajan via ntg-context
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=4ef10093-262f-86cb-395e-fd8650fc37e5@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).