From: Oliver Heins <olli@sopos.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug with overprinting in Mark II/IV?
Date: Sat, 12 Dec 2009 16:41:23 +0100 [thread overview]
Message-ID: <878wd8dwt8.fsf@sopos.org> (raw)
In-Reply-To: <4B228E0D.5080402@gmx.net> (Peter Rolf's message of "Fri, 11 Dec 2009 19:23:09 +0100")
Hi Peter,
Peter Rolf <indiego@gmx.net> writes:
> I get the same 'kind of knockedout' text as in the other example...
> but the black text is set as /DeviceGray and not /DeviceCMYK
> (k-component). You can make this visible by using
> 'Vorschau: Separiert' with the option 'Einblenden: Nicht-DeviceCMYK'.
>
> I think this is just a limitation of the previewer. You can define
> your own cmyk black with \definecolor[myblack][k=1]. I bet that the
> knockedout effect will vanish with cmyk black (untested).
You're right. With k=1, the 'kind of knockedout' vanishes. Thank you
very much, Peter!
So is it advisable to change all black to cmyk black or can I safely
rely on the DeviceGray black?
>> Can you test the following? My Acrobat is on a machine without net, and
>> my usb stick broke within the experiments.
>>
> prepress mess + bad luck => *have a break and enjoy your weekend* :)
Well, due to your kind help, I'm able to do so now :-)
Thanks again,
olli
--
Oliver Heins heins@sopos.org http://oliverheins.net/
http://blog.overheins.net/ F27A BA8C 1CFB B905 65A8
http://scriptorium-adp.de/ 2544 0F07 B675 9A00 D827
1024D/9A00D827 2004-09-24 -- gpg --recv-keys 0x9A00D827
Please avoid sending me Word or PowerPoint attachments:
http://www.gnu.org/philosophy/no-word-attachments.html
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-12-12 15:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 12:53 Oliver Heins
2009-12-11 13:40 ` Peter Rolf
2009-12-11 13:53 ` Taco Hoekwater
2009-12-11 14:41 ` Peter Rolf
2009-12-11 16:32 ` Oliver Heins
2009-12-11 17:35 ` Peter Rolf
2009-12-11 17:57 ` Oliver Heins
2009-12-11 18:18 ` luigi scarso
2009-12-11 18:23 ` Peter Rolf
2009-12-12 15:41 ` Oliver Heins [this message]
2009-12-12 15:46 ` Martin Schröder
2009-12-12 16:17 ` Hans Hagen
2009-12-12 17:43 ` Oliver Heins
2009-12-13 15:20 ` Peter Rolf
2009-12-11 14:07 ` luigi scarso
2009-12-11 16:37 ` Oliver Heins
2009-12-11 16:42 ` luigi scarso
2009-12-11 17:00 ` Oliver Heins
2009-12-11 17:19 ` 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=878wd8dwt8.fsf@sopos.org \
--to=olli@sopos.org \
--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).