ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Harald Koenig <koenig@tat.physik.uni-tuebingen.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: shrink JPGs to some resolution (dpi) ?
Date: Tue, 10 Mar 2015 00:33:48 +0100	[thread overview]
Message-ID: <20150309233348.GA30852@hl.fritz.box> (raw)
In-Reply-To: <alpine.LNX.2.03.1503091742170.1317@hzvpu.rqh>

On Mar 09, Aditya Mahajan wrote:

> Why not eliminate the orignal high quality jpegs altogether? Use

one reason is that the jpgs are not in final shape either.
the selected pictures will be reworked from raw files, 
maybe some brightness/contrast correction, clipped,  etc.

whenever the images are reworked, this will happen on the original pictures
and then the resize/... steps are needed again.

yes I know, makefiles and easy shell scripting  can do all this work (actually they do already;)
but I dream of reducing the number of tools, processing steps, ...

I thought everyone using jpeg images might have the same interest without additional hassle: 
just make my output PDF suitable for printing at 300dpi quality or similar...
runtime potimisation (e.g. caching) is a different topic,
and that also can be solves nicely with lua I'd guess?!;-)


> imagemagick or your favorite photo batch processor to convert all
> the high quality jpegs to low quality jpegs.

ACK -- sort of:  
have a look for my next mail "jpeg problem: Dimension too large"
as I'm running into a strange problem exactly using imagemagick to shrink the images...

and I need information about the rendering size of the image from context (if pictures
are used in different sizes or come from different types of cameras etc.), 
so it's not a imagemagick-only thing.


> Say you have directories images/print that contain 300dpi images and
> images/screen that contain 100dpi images. Then you can use:
> 
> \setupexternalfigures
>     [directory={images/print}]
> 
> \startmode[screen]
> \setupexternalfigures
>     [directory={images/screen}]
> \stopmode
> 
> Run with context --mode=screen to get low-resolution images.

except for the "mode" thing (thanks for that nice context example!!)
that's how my setup looks already!  though I'd like context (lua?) to shrink the images
(and maybe even write to some "cache" directory?  not really needed, but nice idea while typing;-)


thanks,

Harald
-- 
"I hope to die                                      ___       _____
before I *have* to use Microsoft Word.",           0--,|    /OOOOOOO\
Donald E. Knuth, 02-Oct-2001 in Tuebingen.        <_/  /  /OOOOOOOOOOO\
                                                    \  \/OOOOOOOOOOOOOOO\
                                                      \ OOOOOOOOOOOOOOOOO|//
                                                       \/\/\/\/\/\/\/\/\/
Harald Koenig                                           //  /     \\  \
koenig@tat.physik.uni-tuebingen.de                     ^^^^^       ^^^^^
___________________________________________________________________________________
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:[~2015-03-09 23:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 21:12 Harald Koenig
2015-03-09 21:47 ` Aditya Mahajan
2015-03-09 23:33   ` Harald Koenig [this message]
2015-03-10  0:05     ` Hans Hagen
2015-03-09 21:50 ` Alan BRASLAU
2015-03-09 22:10   ` luigi scarso
2015-03-09 22:25   ` Hans Hagen
2015-03-09 23:18     ` Harald Koenig
2015-03-10  0:17       ` Hans Hagen
2015-03-10  1:33         ` Harald Koenig
2015-03-10  6:34           ` Henning Hraban Ramm
2015-03-10 11:12           ` Hans Hagen
2015-03-09 21:54 ` Pablo Rodriguez
2015-03-10  6:44 ` Peter Münster
2015-03-10  7:43   ` Harald Koenig
2015-03-10  9:08     ` 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=20150309233348.GA30852@hl.fritz.box \
    --to=koenig@tat.physik.uni-tuebingen.de \
    --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).