From: Brooks Moses <bmoses@stanford.edu>
Subject: Re: ConTeXt output & commercial printing houses: Thanks!
Date: Mon, 26 Jul 2004 23:33:03 -0700 [thread overview]
Message-ID: <4.3.1.2.20040726232423.017f84f8@cits1.stanford.edu> (raw)
In-Reply-To: <20040727061509.GB17632@swordfish>
At 11:15 PM 7/26/2004, you wrote:
>On Sat, Jul 24, 2004 at 03:21:39PM -0500, Bill McClain wrote:
> > - Also, I don't know whether it is possible to downsample images in
> > PDF's that you generate from ConTeXt. If it is, avoid it.
>
>That raises an important question: if downsampling is done, is it
>obvious what ConTeXt commands cause it to happen?
There's, to my knowledge, no engine in pdfTeX for downsampling images;
there certainly be one coded in ConTeXt. Thus, I'd be fairly confident in
guessing that it is indeed, fairly obvious, on grounds that there are no
commands which do that.
> > The printer
> > expects CMYK images (not RGB!) where the resolution is approx. 2 times
> > the screen count in the final print, @ the physical size on the paper.
> > So if you have an image in your PDF that is 10 cms /4 in. wide, and you
> > want it printed in a 150 lpi (lines per inch) screen, make sure the
> > original resolution is 300 dpi @ 10 cms / 4 in.
>
>Now that's interesting. I imagined you would get the best results with
>images that were designed exactly at the printer resolution.
You might, but that would only be true if you also have the image aligned
exactly with the printer resolution -- which is unlikely to be the case
unless you do it explicitly. Having the 2x-or-higher resolution means that
the downsampling in the printing process will produce an acceptable result
no matter what the alignment is.
Beyond that, I suspect there are also some effects involved in the fact
that the printer is creating a screen rather than dots of pure color; there
are things going on in the screen that are on a finer scale than the line
spacing, and having the higher-resolution to base them on probably produces
a better result.
- Brooks
next prev parent reply other threads:[~2004-07-27 6:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 19:41 ConTeXt output & commercial printing houses Matt Gushee
2004-07-24 20:21 ` Bill McClain
2004-07-24 20:25 ` Siep Kroonenberg
2004-07-25 9:57 ` Henning Hraban Ramm
2004-07-25 10:01 ` Mats Broberg
2004-07-25 11:58 ` Adam Lindsay
2004-07-25 12:03 ` Mats Broberg
2004-07-27 6:15 ` ConTeXt output & commercial printing houses: Thanks! Matt Gushee
2004-07-27 6:33 ` Brooks Moses [this message]
2004-07-27 9:27 ` Siep Kroonenberg
2004-07-27 11:53 ` George N. White III
2004-07-27 15:28 ` Downsampling images in pdfTeX Mats Broberg
2004-07-27 17:47 ` George N. White III
2004-07-27 19:36 ` Vit Zyka
2004-07-28 15:54 ` Peter Münster
2004-07-27 7:36 ` ConTeXt output & commercial printing houses: Thanks! Tobias Hilbricht
2004-07-27 11:47 ` Bill McClain
2004-07-27 15:51 ` Mats Broberg
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=4.3.1.2.20040726232423.017f84f8@cits1.stanford.edu \
--to=bmoses@stanford.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).