From: Christoph Reller <christoph.reller@gmail.com>
To: ntg-context <ntg-context@ntg.nl>
Subject: \pdfbackendcurrentresources not expanded
Date: Mon, 21 Jun 2021 13:58:49 +0200 [thread overview]
Message-ID: <CAO8LnPESN18caznOWOcBqAkvP7j_5LmFAmazs+P5kQHFy7ivvg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 880 bytes --]
Hi,
Consider the following MWE, which uses the tizk module:
\usemodule[tikz]
\usetikzlibrary[fadings]
\starttext
\starttikzpicture
\fill [path fading=west,red] (-1,-1) rectangle (1,1);
\stoptikzpicture
\stoptext
When compiling with ConTeXt LMTX version 2021.06.18, the output PDF
contains "\pdfbackendcurrentresources" in the middle of a resource
dictionary. Apparently, this command does not get expanded but is written
literally to the file, which makes the PDF corrupt.
This command is used in the tikz module file pgfutil-context.def as:
\def\pgf@sys@pdf@possible@resources{\pdfbackendcurrentresources}
As mentioned in a comment in back-pdf.mkxl, the command is implemented in
lua in lpdf-ini.lmt.
The command is also used in mlib-pps.mkxl and is documented in ConTeXts
interface. Can somebody tell why it is not expanded?
Any help is appreciated. Cheers,
Christoph
[-- Attachment #1.2: Type: text/html, Size: 1162 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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:[~2021-06-21 11:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAO8LnPESN18caznOWOcBqAkvP7j_5LmFAmazs+P5kQHFy7ivvg@mail.gmail.com \
--to=christoph.reller@gmail.com \
--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).