From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: access image properties in Lua
Date: Tue, 18 Jul 2023 13:39:04 +0200 [thread overview]
Message-ID: <4f4033cb-82c6-9fbf-bfe5-e7573404e43a@fiee.net> (raw)
In-Reply-To: <048d051e-c66f-3e0f-e3d2-48ef300b7280@icloud.com>
(I assume you didn’t reply privately on purpose and take this back to
the mailing list.)
Am 18.07.23 um 12:47 schrieb Alan Braslau:
> P.S. I have not used the built-in resolution= image conversion (using
> gm/ImageMagik). I imagine that ConTeXt is clever enough to store the
> converted file so that it only need to be converted once. However, is
> the resolution resampled before or after size conversion in
> \externalfigure?
If Hans didn’t add it recently, there‘s no automatical downsampling in
ConTeXt (yet), that’s why I want to do this; the resolution parameter is
apparently never used.
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-07-18 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 12:22 Henning Hraban Ramm
2023-07-13 7:19 ` Hans Hagen
2023-07-17 13:44 ` [NTG-context] " Alan Braslau via ntg-context
2023-07-17 16:20 ` Henning Hraban Ramm
2023-07-17 17:10 ` Alan Braslau via ntg-context
[not found] ` <048d051e-c66f-3e0f-e3d2-48ef300b7280@icloud.com>
2023-07-18 11:39 ` Henning Hraban Ramm [this message]
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=4f4033cb-82c6-9fbf-bfe5-e7573404e43a@fiee.net \
--to=texml@fiee.net \
--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).