ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau <braslau.list@comcast.net>
To: "Peter Münster" <pm@a16n.net>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: degrade module
Date: Mon, 18 Feb 2019 16:21:18 -0700	[thread overview]
Message-ID: <20190218162118.1a131073@comcast.net> (raw)
In-Reply-To: <87a7isognj.fsf@a16n.net>

On Mon, 18 Feb 2019 23:50:24 +0100
Peter Münster <pm@a16n.net> wrote:

> On Mon, Feb 18 2019, Alan Braslau wrote:
> 
> > Incorrect, an image file contains width and height (in pixels) as well as a
> > resolution,  
> 
> Optionally a resolution in the metadata. Then, of course, you have a
> "natural size". But that doesn't matter, if you want other dimensions.

For example, in Context

\externalfigure [myfigure]

should give this natural size. Of course, you can always specify other dimensions,
in which case it gets scaled. Since what counts for our use in Context is usually
fixing a particular size, i.e. [width=\textwidth], the "resolution", i.e. density
in pixels is something that we want to control. So if we want to print to 300 dpi,
for example, and we have a text width of 17cm, say, then we would like to have an
image that is some 2000 pixels in width. One can normalize one's collection of
images however one wishes, but manipulating them on the fly as one changes layout
or image placement hardly seems efficient, even if one were to be clever in storing
copies and looking at time stamps. A little bit of forethought might be better, and
more predictable.

Alan
___________________________________________________________________________________
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:[~2019-02-18 23:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 19:49 Lutz Haseloff
2019-02-14 20:22 ` Marco Patzer
2019-02-14 20:37   ` Peter Münster
2019-02-14 20:32 ` Peter Münster
2019-02-14 20:41   ` Wolfgang Schuster
2019-02-14 21:00     ` Peter Münster
2019-02-14 20:44   ` Hans Hagen
2019-02-15  6:56     ` Lutz Haseloff
2019-02-15  7:24       ` Henning Hraban Ramm
2019-02-15  7:25       ` Marco Patzer
2019-02-15  9:22         ` Lutz Haseloff
2019-02-15 10:08           ` Marco Patzer
2019-02-15 10:48             ` Lutz Haseloff
2019-02-15 11:23               ` Marco Patzer
2019-02-17 11:14                 ` Peter Münster
2019-02-18  9:13                   ` Marco Patzer
2019-02-18 10:03                     ` Peter Münster
2019-02-18 15:25                     ` Alan Braslau
2019-02-18 21:09                       ` Peter Münster
2019-02-18 21:23                         ` Alan Braslau
2019-02-18 22:50                           ` Peter Münster
2019-02-18 23:21                             ` Alan Braslau [this message]
2019-02-19  9:42                               ` Peter Münster

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=20190218162118.1a131073@comcast.net \
    --to=braslau.list@comcast.net \
    --cc=ntg-context@ntg.nl \
    --cc=pm@a16n.net \
    /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).