ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: jbf via ntg-context <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: help with facing page image
Date: Thu, 10 Mar 2022 00:35:57 -0500 (EST)	[thread overview]
Message-ID: <nycvar.YAK.7.78.908.2203100034470.18317@nqv-guvaxcnq> (raw)
In-Reply-To: <fdccb785-2c71-1ff2-0af8-6c3a4bbfa295@gmail.com>

On Thu, 10 Mar 2022, jbf via ntg-context wrote:

> Am endeavouring to explore Wolfgang's very 'elegant' solution to this 
> facing page challenge. The exploration has included a look at 
> base/mkxl/page-inj.mklx (thanks Sreeram for reminding me of this) where 
> I see immediately that the approach is experimental and where it says 
> also that 'probably more alternatives will be added'. I wonder if that 
> last phrase also includes the ability to manipulate the image(s) either 
> generally or in individual cases?
> 
> So, for example., say I need (and in fact I do!) to change some aspect 
> of individual images, e.g. I might want to scale=500, or fiddle with 
> width/height of a particular image. At the moment I cannot see a way of 
> doing this for each image. I wondered if the commented out setups in the 
> response to this question might be a clue, but so far haven't been able 
> to get that to have any effect.

Couldn't you just pass scale as a key-value parameter, similar to how `name` is passed in Wolfgang's solution?

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
___________________________________________________________________________________

  reply	other threads:[~2022-03-10  5:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  3:49 jbf via ntg-context
2022-03-07  5:38 ` śrīrāma via ntg-context
2022-03-07  5:41   ` śrīrāma via ntg-context
2022-03-07  6:20   ` jbf via ntg-context
2022-03-07  7:01     ` śrīrāma via ntg-context
2022-03-07  8:27       ` jbf via ntg-context
2022-03-07 18:35         ` Wolfgang Schuster via ntg-context
2022-03-08  2:51           ` śrīrāma via ntg-context
2022-03-08  3:46             ` śrīrāma via ntg-context
2022-03-09 22:02           ` jbf via ntg-context
2022-03-10  5:35             ` Aditya Mahajan via ntg-context [this message]
2022-03-10  5:48               ` jbf via ntg-context
2022-03-10  6:51             ` śrīrāma via ntg-context
2022-03-10  8:49               ` jbf via ntg-context
2022-03-11 12:36             ` Wolfgang Schuster via ntg-context
2022-03-11 23:50               ` jbf via ntg-context
2022-03-08  0:52       ` jbf via ntg-context
2022-03-07 20:08 ` Bruce Horrocks via ntg-context
2022-03-07 20:23   ` Henning Hraban Ramm 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=nycvar.YAK.7.78.908.2203100034470.18317@nqv-guvaxcnq \
    --to=ntg-context@ntg.nl \
    --cc=adityam@umich.edu \
    /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).