<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <style type="text/css" style="display:none;"></style> </head> <body dir="ltr"> <div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr"> <p style="margin-top:0;margin-bottom:0"><span>ghostscript had a similar issue with performance, and they added a -dUseFastColor to bypass ICC lookups. <a href="https://www.ghostscript.com/doc/9.23/Use.htm#EPS_parameters" class="OWAAutoLink" id="LPlnk281537" previewremoved="true">https://www.ghostscript.com/doc/9.23/Use.htm#EPS_parameters</a></span><br> </p> <p style="margin-top:0;margin-bottom:0"><span>They are also working on a fork of LCMS that is faster and thread-safe. <a href="https://www.ghostscript.com/doc/9.23/History9.htm#Version9.23" class="OWAAutoLink" id="LPlnk824098" previewremoved="true">https://www.ghostscript.com/doc/9.23/History9.htm#Version9.23</a></span><br> </p> <p style="margin-top:0;margin-bottom:0"><span><br> </span></p> <p style="margin-top:0;margin-bottom:0"><span>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.</span></p> <p style="margin-top:0;margin-bottom:0"><span><br> </span></p> <p style="margin-top:0;margin-bottom:0"><span>William</span></p> <br> <br> <div style="color: rgb(0, 0, 0);"> <hr style="display:inline-block;width:98%" tabindex="-1"> <div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> poppler <poppler-bounces@lists.freedesktop.org> on behalf of Carlos Garcia Campos <carlosgc@gnome.org><br> <b>Sent:</b> Monday, June 11, 2018 9:10 AM<br> <b>To:</b> poppler@lists.freedesktop.org<br> <b>Subject:</b> [poppler] Color conversion while rendering for printing</font> <div> </div> </div> <div class="BodyFragment"><font size="2"><span style="font-size:11pt;"> <div class="PlainText"><br> Hi,<br> <br> does it make sense to do color conversions using CMS while rendering<br> document for printing? I don't know much about CMS, I'm asking because<br> libcms is very very slow in some documents. When rendering individual<br> pages like viewers do, the slowdown is not that noticeable, but when<br> printing an entire document the slowdown is very annoying. I think we<br> could use the existing printing flag we pass when creating the GfxState<br> to not use CMS. <br> <br> Thanks,<br> -- <br> Carlos Garcia Campos<br> PGP key: <a href="http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x523E6462" id="LPlnk793467" class="OWAAutoLink" previewremoved="true"> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x523E6462</a><br> </div> </span></font></div> </div> </div> </body> </html>