ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Kip Warner <kip@thevertigo.com>
Subject: Re: Rendering differences between PDF viewers
Date: Wed, 18 Apr 2012 13:12:34 +0200	[thread overview]
Message-ID: <4F8EA1A2.3030806@gmx.net> (raw)
In-Reply-To: <4F8E6F65.50002@wxs.nl>

Am 18.04.2012 09:38, schrieb Hans Hagen:
> On 18-4-2012 02:49, Kip Warner wrote:
>> On Tue, 2012-04-17 at 12:48 +0200, Peter Rolf wrote:
>>> Hi Kip,
>>>
>>> give it a try and add this to you document...
>>>
>>>
>>> \startluacode
>>>
>>> backends                = backends                or { }
>>> backends.codeinjections = backends.codeinjections or { }
>>>
>>> function backends.codeinjections.rgbtransparencygroup()
>>>      local d = lpdf.dictionary {
>>>          S  = lpdf.constant("Transparency"),
>>>          CS = lpdf.constant("DeviceRGB"),
>>>          I  = true }
>>>      lpdf.registerpagefinalizer(function()
>>> lpdf.addtopageattributes("Group",d) end)
>>> end
>>>
>>> backends.codeinjections.rgbtransparencygroup()
>>>
>>> \stopluacode
>>>
>>>
>>> This does not work, if you also use CMYK based graphics/pictures in your
>>> document (as this is done document wide).
>>
>> You know Peter, I must admit. ConTeXt has made me rather cynical at
>> times. I don't know how many times I've tried a snippet of this or that,
>> only to have it do exactly what I hadn't intended. Having said that,
>> every now and then I am blown away when something I never expected to
>> actually get working, gets working. Thank you so much, that worked
>> beautifully. Both Evince (poppler based) and AR look identical now.
>>
>> I stuck it in my environment file. I wonder if there is a safer way of
>> doing this than via "inline asm", so to speak. Also, maybe for my
>> benefit, and anybody else having the same problem, you might be able to
>> explain what was happening?
> 
> At some point it can become an option (or semi automatic) but the
> problem is that we don't know in advance if we operate in rgb or cmyk. I
> can imagine that when we have enabled cmyk and disabled rgb or reverse,
> it can be added automatically but even then users must make sure that
> all images are in the right colorspace as well. And what with spotcolors?
> 
> Hans
> 
I understand that there is no easy or general solution for this.
But on the other hand is PNG currently the only way to use transparent
bitmaps in TeX. The usage of transparent PNG is quite common, so this is
a general problem that should be solved.

I like your idea of automatically adding such groups, if the user
declares the color space beforehand. Also no answer for the spot color
problem, but as long as the user does not limit the used color spaces,
things can stay as they are. Just my 2 cents.

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


  reply	other threads:[~2012-04-18 11:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15  6:00 Kip Warner
2012-04-15  9:07 ` Mojca Miklavec
2012-04-16 23:43   ` Kip Warner
2012-04-15 16:00 ` Hans Hagen
2012-04-16 23:44   ` Kip Warner
2012-04-17  6:54     ` Hans Hagen
2012-04-17  6:57       ` Kip Warner
2012-04-17  9:53         ` Peter Rolf
2012-04-17 10:12           ` Hans Hagen
2012-04-17 10:48             ` Peter Rolf
2012-04-18  0:49               ` Kip Warner
2012-04-18  6:47                 ` Martin Schröder
2012-04-18  7:19                   ` luigi scarso
2012-04-18 10:58                     ` Martin Schröder
2012-04-19 18:26                       ` Hans Hagen
2012-04-18 22:54                   ` Kip Warner
2012-04-18  7:38                 ` Hans Hagen
2012-04-18 11:12                   ` Peter Rolf [this message]
2012-04-19 18:25                     ` Hans Hagen
2012-04-20  7:50                       ` Peter Rolf
2012-04-24 12:42                         ` Hans Hagen
2012-04-24 13:37                           ` Peter Rolf
2012-04-25 16:08                             ` Peter Rolf
2012-04-24 23:34                           ` Kip Warner
2012-04-28 15:52                           ` Peter Rolf
2012-04-28 18:25                             ` Kip Warner
2012-04-18 22:58                   ` Kip Warner
2012-04-18  0:26           ` Kip Warner
2012-04-17  7:12       ` Alan BRASLAU
2012-04-17  7:31         ` luigi scarso
2012-04-17  7:42           ` Hans Hagen
2012-04-17  8:05             ` luigi scarso
2012-04-18  0:24           ` Kip Warner
2012-04-17 18:57         ` Kip Warner
     [not found] ` <CAPm68ZimT3cbuhwqTgG+OXXiA_RHaA2snOT05rO-J_iWjodCQA@mail.gmail.com>
2012-04-18  0:21   ` Kip Warner

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=4F8EA1A2.3030806@gmx.net \
    --to=indiego@gmx.net \
    --cc=kip@thevertigo.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).