From: Peter Rolf <indiego@gmx.net>
To: ntg-context@ntg.nl
Subject: Re: compresslevel and png graphics (mkiv)
Date: Fri, 27 May 2011 13:57:51 +0200 [thread overview]
Message-ID: <4DDF91BF.8030806@gmx.net> (raw)
In-Reply-To: <4DDE7D0F.3030002@gmx.net>
Am 26.05.2011 18:17, schrieb Peter Rolf:
> Am 26.05.2011 12:52, schrieb Peter Rolf:
>> Am 25.05.2011 21:54, schrieb Hartmut Henkel:
> [..]
>>>
>>> no. There is a "PNG Copy" function for literal embedding of the PNG
>>> file, but that triggers only, if the file simultaneously satisfies quite
>>> a few conditions, which are about: non-interlaced, no palette, no
>>> transparency, no gamma coming with it, no gamma modification requested,
>>> no white adjustment in the PNG, and a few more rare others. Else it's
>>> de-compressed and then re-compressed to the \pdfcompresslevel, and
>>> additional streams and dicts are added. You see in the log if it finally
>>> was "PNG Copy" or not.
>>>
> [..]
>>>
>>> These are about the factors affecting the PNG to PDF size. For your big
>>> PNG graphic you may find a preprocessing (e. g., pngtopnm | pnmtopng
>>> will definitely remove all fat) that makes it compliant with the "PNG
>>> copy".
>>>
>> I will give that a try. But I doubt that there is much 'fat' on that
>> graphic. Anyhow, you never know before you have tried it. :-)
>>
>
> No luck. I used imagemagick to convert to pnm and back.
> Transparency was removed before by adding a white background, also all
> not critical chunks (ICC profile, backgroundcolor, resolution, creation
> and modify date, comment) were removed. The graphic is a valid PNG
> (TweakPNG) and aside from the size, there is nothing special with this
> graphic. Still no '(PNG copy)'.
>
> @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 for any inconvenience. I should have tested this case before...
Best wishes, Peter
> Regards, 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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:[~2011-05-27 11:57 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 [this message]
2011-05-27 13:09 ` Hartmut Henkel
2011-05-27 15:11 ` Peter Rolf
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=4DDF91BF.8030806@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).