ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sietse Brouwer <sbbrouwer@gmail.com>
To: Guy Stalnaker <jstalnak@wisc.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Images in MultiMarkdown -> context -> PDF
Date: Wed, 21 Nov 2012 21:36:59 +0100	[thread overview]
Message-ID: <CAF=dkzwS_RXRNYprSZEZwwkxTGVQdadeXD9kQSmXWdWG-kjEDw@mail.gmail.com> (raw)
In-Reply-To: <50AD1AAA.1040302@wisc.edu>

Guy wrote:
> Well, that lead to an interesting experiment. I used convert to -resample a
> set of images to 300dpi and redid the compile. They are all now too bod,
> many off the right side of the page. Then did the same but set to 72. They
> are still too big. Odd, from too small to too big.

I think you don't want -resample, but -density:

# density given in dpi
convert pic.jpg -density 72 pic-out.jpg

convert -density keeps the pixel size and changes the display size by
setting the density metadata.
convert -resample keeps the display size and changes the pixel size by
resampling at a certain density. (This explains why the picture
remained the same too-large size when you resampled at 72 and 300
dpi.)

Because you want to change the display size (and also because
resampling is a lossy process), I think you want -density.

As for the density value you want to use:
Your picture is 547px wide, so if you want it to display it 3 inches
wide you should set its density metadata to 547/3 = 183 dpi.

Does this work?
All the best,
Sietse
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2012-11-21 20:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21  4:42 Guy Stalnaker
2012-11-21 10:07 ` Martin Schröder
2012-11-21 13:21   ` Guy Stalnaker
2012-11-21 14:35     ` Sietse Brouwer
2012-11-21 14:55       ` Guy Stalnaker
2012-11-21 17:44         ` Peter Rolf
     [not found]         ` <CAF=dkzwfNWgMQpGe3HXeuAZxpCjmzvJTHxxb-2pK6zKJ3+uBPw@mail.gmail.com>
2012-11-21 18:17           ` Guy Stalnaker
2012-11-21 20:36             ` Sietse Brouwer [this message]
2012-11-23 21:34               ` Guy Stalnaker
2012-11-23 21:45                 ` Aditya Mahajan
2012-11-23 23:25               ` Guy Stalnaker

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='CAF=dkzwS_RXRNYprSZEZwwkxTGVQdadeXD9kQSmXWdWG-kjEDw@mail.gmail.com' \
    --to=sbbrouwer@gmail.com \
    --cc=jstalnak@wisc.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).