From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug with overprinting in Mark II/IV?
Date: Fri, 11 Dec 2009 18:35:46 +0100 [thread overview]
Message-ID: <4B2282F2.1000200@gmx.net> (raw)
In-Reply-To: <87zl5pfp47.fsf@sopos.org>
[-- Attachment #1.1: Type: text/plain, Size: 2339 bytes --]
Oliver Heins schrieb:
> Hi Peter,
>
> Peter Rolf <indiego@gmx.net> writes:
>
>
>> Oliver Heins schrieb:
>>
>>> Hello,
>>>
>>> with color black overprinting is not working. You can easily spot this
>>> when you use the »Ausgabevorschau« (sorry, my acrobat is in german
>>> locale, must be something with »preview« in english; located in the
>>> »tools« menu) in acrobat and remove magenta and black from the preview.
>>> Whilst under the region with the magenta colored text the picture gets
>>> shown, in the region with the black colored text the text is cut out of
>>> the picture, leaving white.
>>>
>>>
>>>
>> I think the visible 'knockedout' text on the picture is just another
>> acrobat bug. I manually checked the text and the OVP attributes are
>> correctly set. If you use the coloring mechanism (Ausgabenvorschau ->
>> Farbwarnungen -> [x] Überdruck anzeigen), you will see that everything
>> looks ok.
>>
>
> Yes, I noticed that, too. But to me it looks like it is first knocked
> out in the pdf, and then the overprint flag is set.
>
>
Good point. In that case the text must be set twice, as knockout and
overprint can't coexist. I have looked into the uncompressed mkii PDF
(\nopdfcompression) and I can not see any obvious flaw. The parts are
clearly separeted by '/GSknockout gs' and '/GSoverprint gs', the black
text is not set twice.
Just an idea: the colorspace of the picture is RGB, the text is set in
CMYK. Maybe the mixed color spaces mess up things here.
> I made a document with scribus, which looks alright in acrobats preview:
> http://www.sopos.org/olli/overprinting-scribus.pdf
>
>
Same here. The difference is, that the picture here is also set in CMYK.
So this points to the 'colorspace mess' theory too ;)
> So I doubt that this is a bug in acrobat, but in context or even in
> pdftex/luatex.
>
>
>>> you have to manually copy the hacker.jpg to your working directory
>>> (under linux e.g. with cp $(kpsewhich hacker.jpg)
>>> /path/to/your/working/directory) and change the path to make the
>>> minimal example work under mark iv.
>>>
>> I noticed this too (no picture with mkiv). BOF = Bug Or Feature :)
>>
>
> Feature, as Taco kindly pointed out :-)
>
> Regards,
> olli
>
>
[-- Attachment #1.2: Type: text/html, Size: 3238 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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-11 17:35 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 [this message]
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
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=4B2282F2.1000200@gmx.net \
--to=indiego@gmx.net \
--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).