[poppler] Color conversion while rendering for printing
williambader at hotmail.com
Mon Jun 11 14:02:45 UTC 2018
ghostscript had a similar issue with performance, and they added a -dUseFastColor to bypass ICC lookups. https://www.ghostscript.com/doc/9.23/Use.htm#EPS_parameters
They are also working on a fork of LCMS that is faster and thread-safe. https://www.ghostscript.com/doc/9.23/History9.htm#Version9.23
I think that only the final application to process the file should apply the color conversion. Viewers know that they are the final application. When poppler renders a document, it doesn't know if the results will be sent to another application, to a printer that will apply its own color conversion, or to a printer that will output it directly. That might be another reason to make it optional.
From: poppler <poppler-bounces at lists.freedesktop.org> on behalf of Carlos Garcia Campos <carlosgc at gnome.org>
Sent: Monday, June 11, 2018 9:10 AM
To: poppler at lists.freedesktop.org
Subject: [poppler] Color conversion while rendering for printing
does it make sense to do color conversions using CMS while rendering
document for printing? I don't know much about CMS, I'm asking because
libcms is very very slow in some documents. When rendering individual
pages like viewers do, the slowdown is not that noticeable, but when
printing an entire document the slowdown is very annoying. I think we
could use the existing printing flag we pass when creating the GfxState
to not use CMS.
Carlos Garcia Campos
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x523E6462
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the poppler