ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Color separation
Date: Thu, 17 Mar 2005 17:52:40 +0100	[thread overview]
Message-ID: <4239B5D8.4000305@wxs.nl> (raw)
In-Reply-To: <423995A4.30707@capdm.com>

Duncan Hothersall wrote:
> Sorry for all the messages; I am exploring things I don't really 
> understand. I hope someone can enlighten me!
> 
> With the following colour set-up:
> 
> \setupcolors[rgb=no,cmyk=yes,spot=yes,state=start]
> \definecolor[PantoneTwoNineFour][c=1,m=.56,y=0,k=.18]
> \definecolor[IFSbluetabletint][PantoneTwoNineFour][p=.15]
> 
> and then using this tint as a textbackground and also as a 
> backgroundcolor in frames, I am getting complaints from my printers that 
> black overprinted on the tint is 'knocking out' the tint and leaving 
> white on the separated plate.
> 
> I have read and re-read the useful msplit.pdf which suggests that the 
> implicit criterium=all will negate this effect, but perhaps I have 
> misunderstood?
> 
> Two questions:
> 1. how can I stop black overprinting from knocking out the tint, and
> 2. is there a way I can check that it is working properly without 
> sending it to the printer each time?
> 
> Thanks as ever for any help. Do I need to post example output?

whow, a demanding color user -)

see mag-0006.pdf for more info on properties


\setupcolors[state=start,textcolor=cyan,overprint=yes]

\setupbackgrounds[page][background=color,backgroundcolor=magenta]

\starttext

\input tufte

\startproperty[knockout]\input tufte\stopproperty

\startproperty[overprint]\input tufte\stopproperty

\input tufte

\stoptext



-----------------------------------------------------------------
                                           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
-----------------------------------------------------------------

  parent reply	other threads:[~2005-03-17 16:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 14:35 Duncan Hothersall
2005-03-17 15:44 ` Henning Hraban Ramm
2005-03-17 16:52 ` Hans Hagen [this message]
2005-03-17 17:02   ` Adam Lindsay
     [not found] <20050317170134.1400D1293C@ronja.ntg.nl>
2005-03-17 17:11 ` Duncan Hothersall
  -- strict thread matches above, loose matches on Subject: below --
2005-03-17 16:58 Duncan Hothersall
2005-03-18  8:36 ` Hans Hagen
     [not found] <Your message of "Thu, 13 Sep 2001 12:56:53 +0200." <5.1.0.14.1.20010913125448.022ece30@server-1>
2001-09-13 11:25 ` Joop Susan
2001-09-13 12:00   ` Hans Hagen
     [not found] <Your message of "Thu, 13 Sep 2001 11:14:03 +0200." <5.1.0.14.1.20010913111303.022dfdc0@server-1>
2001-09-13 10:15 ` Joop Susan
2001-09-13 10:56   ` Hans Hagen
2001-09-13 11:23   ` Taco Hoekwater
2001-09-15 17:58     ` Henning Hraban Ramm
2001-09-13  8:35 Joop Susan
2001-09-13  9:14 ` Hans Hagen
2000-12-02 12:45 color separation Hraban
2000-12-02 15:38 ` George N. White III
2000-12-02 20:32 ` siepo
2000-12-03 14:36   ` Hraban
2000-12-04 21:48   ` Hraban
2000-12-05  8:05     ` Hans Hagen

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=4239B5D8.4000305@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).