ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: Harald Koenig <koenig@tat.physik.uni-tuebingen.de>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: shrink JPGs to some resolution (dpi) ?
Date: Tue, 10 Mar 2015 01:17:29 +0100	[thread overview]
Message-ID: <54FE3819.4030805@wxs.nl> (raw)
In-Reply-To: <20150309231806.GA22736@hl.fritz.box>

On 3/10/2015 12:18 AM, Harald Koenig wrote:
> On Mar 09, Hans Hagen wrote:
>
>> On 3/9/2015 10:50 PM, Alan BRASLAU wrote:
>>
>>> This can be done once and is much better than getting ConTeXt to
>>> convert every time on the fly.
>>
>> Do you really think that we let context convert a big file each run
>> in a critical workflow? Context will only resample when an image
>> file changed (which happens when you have to process from
>> repositories updated by authors).
>
> I guess that's a question for me ?

More for Alan.

> of course I don't plan to run context on the big files every time -- as I know that that's still way too slow;)
> but it would be nice if I don't need magic external tools to guess
> the correct physical print size, calculate the actual number of pixels for e.g. 300 dpi, etc.

150 pixels is probably enough for color print ... if you have raw files 
you can also consider png

anyway, i need to think a bit about it but we do have all the info 
available, like

- needed width/height
- original width/height

and from that we can calculate some conversion parameters

if it would help you i can provide a tracker that will save info like 
this (per image):

  ["used"]={
   ["colordepth"]=0,
   ["depth"]=0,
   ["format"]="pdf",
   ["fullname"]="t:/sources/cow.pdf",
   ["height"]=13156352,
   ["name"]=false,
   ["pages"]=1,
   ["path"]=false,
   ["suffix"]=false,
   ["width"]=18089984,
   ["xresolution"]=0,
   ["xsize"]=18089984,
   ["yresolution"]=0,
   ["ysize"]=13156352,
  },

> finally I like the idea to be able to create the final PDF in a "single" context run
> from *original* source (== original JPGs) without lots of additional tools and steps/scripts
> (or if I want to start over "form scratch" from input files).

that is what we also prefer: only luatex/mkiv + gm / gs

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-10  0:17 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
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 [this message]
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=54FE3819.4030805@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=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).