ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: compresslevel and png graphics (mkiv)
Date: Fri, 27 May 2011 17:11:53 +0200	[thread overview]
Message-ID: <4DDFBF39.9070100@gmx.net> (raw)
In-Reply-To: <20110527130914.171040@gmx.net>

Am 27.05.2011 15:09, schrieb Hartmut Henkel:
>>> @luigi: an ICC profile definitely breaks the <png copy> rules
>>>
>>> The only chunks left are
>>>
>>> IHDR    PNG image header: 5900x4094, 8bits/sample, truecolor,
>> noninterlaced
>>> IDAT    PNG image data
>>> ..
>>> IDAT    PNG image data
>>> IEND    end-of-image marker
>>>
>>> Mh, where is the show stopper? The compression method?
>>>
>> Looks like some of ConTeXt PDF/X-related settings is causing this. If I
>> reduce the code to the pure picture, the '(PNG copy)' is triggered.
>> Probably the active color management (default color space) is breaking
>> the copy process here.
> 
Sorry Hartmut, my last statement is complete BS. I made a 'blind' run in
my lunch break, not inspecting the pdf. And sadly I had forgotten, that
I changed the test file yesterday to use a small png test graphic
instead of my big png. *brain vs. full stomach: 0:1*

So the PDF/X settings have no influence on this. The big png is not
'copied'.
Anyhow, this is not a serious problem and honestly I don't have that
much time now. When I have some more time I will use gdb to find the
failing condition in writepng.w. Will be interesting, the last time I
used gdb is more than 10 years ago.

Thanks for all answers so far.

Regards, Peter

> must be some \pdfimageapplygamma > 0, only this and the \pdfimagehicolor
> primitive can influence this low level stuff.
> 
> Btw, just \pdfimageapplygamma > 0 (without setting \pdfgamma and \pdfimagegamma) already changes the PNG image, since the luatex (and pdftex) internal defaults are not gamma-neutral. No idea if (and then
> to which value) this should be fixed.
> 
> Regards, Hartmut

___________________________________________________________________________________
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:[~2011-05-27 15:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 12:43 Peter Rolf
2011-05-25 14:39 ` Hans Hagen
2011-05-25 14:48   ` Taco Hoekwater
2011-05-25 16:05     ` Peter Rolf
2011-05-25 19:54   ` Hartmut Henkel
2011-05-26 10:52     ` Peter Rolf
2011-05-26 11:22       ` luigi scarso
2011-05-26 16:17       ` Peter Rolf
2011-05-27 11:57         ` Peter Rolf
2011-05-27 13:09           ` Hartmut Henkel
2011-05-27 15:11             ` Peter Rolf [this message]
2011-05-27 15:19               ` luigi scarso
2011-05-27 15:34                 ` Peter Rolf
2011-05-25 14:40 ` Hans Hagen
2011-05-26 17:32   ` mathew
2011-05-26 17:43     ` mathew
2011-05-27  6:17       ` Henning Hraban Ramm
2011-05-27  7:43         ` Hans Hagen
2011-05-26 17:55     ` mathew
2011-05-26 17:58   ` Martin Schröder
2011-05-26 22:52   ` George N. White III

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=4DDFBF39.9070100@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).