ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Black generation in cmyk output
Date: Thu, 02 Dec 2004 10:46:25 +0100	[thread overview]
Message-ID: <41AEE471.7030902@wxs.nl> (raw)
In-Reply-To: <20041202094007.GB1269@mnw.art.pl>

Piotr Kopszak wrote:
> On Wed, Dec 01, 2004 at 05:52:09PM +0100, Hans Hagen wrote:
> 
>>Henning Hraban Ramm wrote:
>>
>>>Am 01.12.2004 um 15:19 schrieb Piotr Kopszak:
>>>
>>>
>>>>Sorry for imprecise question. I meant black generation in rgb images
>>>>in JPG format included in document. If it's not possible to control
>>>>the amount of black in that case I'd like to use cmyk JPG images, but
>>>>will they be left untouched by the colour conversion mechanism?
>>>
>>>
>>>AFAIK ConTeXt doesn't touch pixel images at all - that would be a rather 
>>>complicated task, perhaps using little_cms or GIMP libraries or the like...
>>
>>indeed, however, you may expect some manipulations without touching the 
>>bitmap, like runtime turning gray scales into spot colors and duotones; i 
>>have something running here for half a year now but i recently moved the 
>>code into the kernel
>>
>>Hans
> 
> 
> Right, but what exactly happens with included rgb bitmaps 
> when I use: 
> 
> \setupcolors[state=start,cmyk=yes,rgb=no] 
> 
> Will they be left in rgb? 

bitmaps will not be touched by context, so they will stay rgb (i'm currently 
cleaning up some figure postprocessign code, so meybe that end up in the 
distribution)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2004-12-02  9:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 15:06 Piotr Kopszak
2004-11-30 15:22 ` Taco Hoekwater
2004-11-30 23:19   ` Tex Live 2004 + context Ciro A. Soto
2004-11-30 23:45     ` Patrick Gundlach
2004-11-30 23:52       ` Ciro A. Soto
2004-12-01  0:36         ` Patrick Gundlach
2004-12-01  8:19           ` Taco Hoekwater
2004-12-01  9:22         ` VnPenguin
2004-12-01  9:39           ` Adam Lindsay
2004-12-01 10:45             ` VnPenguin
2004-12-01 14:19   ` Black generation in cmyk output Piotr Kopszak
2004-12-01 16:31     ` Henning Hraban Ramm
2004-12-01 16:52       ` Hans Hagen
2004-12-02  9:40         ` Piotr Kopszak
2004-12-02  9:46           ` Hans Hagen [this message]
2004-12-02 10:10           ` Taco Hoekwater
2004-12-03  8:21             ` Christopher Creutzig
2004-12-03 10:00             ` Piotr Kopszak
2004-12-03 10:15               ` Taco Hoekwater
2004-12-03 17:23               ` Siep Kroonenberg
2004-12-07  9:40             ` Tobias Hilbricht
2004-12-07 10:56               ` Siep Kroonenberg

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=41AEE471.7030902@wxs.nl \
    --to=pragma@wxs.nl \
    --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).