From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Undefined control sequence: \pdfpxdimen
Date: Mon, 22 Jun 2020 18:04:43 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YAK.7.78.908.2006221804380.720622@nqv-guvaxcnq> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2006221752560.720622@nqv-guvaxcnq>
On Mon, 22 Jun 2020, Aditya Mahajan wrote:
> Replying to an old thread ... but drops module does not work with lmtx
> because
> \pxdimen is not defined.
>
> On Thu, 10 Mar 2016, Hans Hagen wrote:
>
>> On 3/10/2016 12:03 AM, Aditya Mahajan wrote:
>>> The drops module uses the primitive \pdfpxdimen in a couple of places,
>>> but that is no longer defined in the current beta. What is the
>>> equivalent command now?
>>>
>>> Examples of usage:
>>>
>>> \pdfpxdimen1in\relax\divide\pdfpxdimen\numexpr\dropsparameter\c!
>>> resolution\relax % set actual pixel dimension
>>
>> just \pxdimen (as it's not related to pdf)
>
> What will be the equivalent of \pxdimen in LMTX?
Just realized that this is a bug in t-drops: Line 143 of t-dropx.mkiv says
\doifundefined{pdfvariable} {\let\pxdimen\pdfpxdimen} % \pxdimen in luatex 0.85
Commenting that out fixes the bug.
Aditya
___________________________________________________________________________________
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:[~2020-06-22 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 23:03 Aditya Mahajan
2016-03-09 23:08 ` Aditya Mahajan
2016-03-09 23:15 ` Hans Hagen
2020-06-22 21:53 ` Aditya Mahajan
2020-06-22 22:04 ` Aditya Mahajan [this message]
2016-03-09 23:46 ` Peter Rolf
2016-03-10 0:00 ` Aditya Mahajan
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=nycvar.YAK.7.78.908.2006221804380.720622@nqv-guvaxcnq \
--to=adityam@umich.edu \
--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).