From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Kip Warner <kip@thevertigo.com>
Subject: Re: Rendering differences between PDF viewers
Date: Sun, 15 Apr 2012 18:00:05 +0200 [thread overview]
Message-ID: <4F8AF085.6070208@wxs.nl> (raw)
In-Reply-To: <1334469628.3748.29.camel@kip-laptop>
On 15-4-2012 08:00, Kip Warner wrote:
> Hey list,
>
> I've noticed an unfortunate visual difference in my document's colours
> when rendered with Evince 2.32.0 where they come out as expected (or
> even with Zathura) against Adobe Reader 9.5.7.
>
> Rendered with Evince 2.32.0:
> https://www.avaneya.com/temp/evince.png
>
> Rendered with Adobe Reader 9.5.7:
> https://www.avaneya.com/temp/reader.png
>
> Note how the latter is overly saturated in the red. Does anyone have any
> clues as to why this might happen and what I might do to make it appear
> as intended in Adobe Reader? I wonder if this might have something to do
> with different renderer's different gamma correction?
>
> It's kind of funny that this could happen because I thought the whole
> point of PDFs was that they were truly portable.
keep in mind that acrobat has monitor profiles, simulates paper and has
different rendering code when transparencies are used
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2012-04-15 16:00 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 [this message]
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
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=4F8AF085.6070208@wxs.nl \
--to=pragma@wxs.nl \
--cc=kip@thevertigo.com \
--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).