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. William ________________________________ From: poppler <[email protected]> on behalf of Carlos Garcia Campos <[email protected]> Sent: Monday, June 11, 2018 9:10 AM To: [email protected] Subject: [poppler] Color conversion while rendering for printing Hi, 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. Thanks, -- Carlos Garcia Campos PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x523E6462
_______________________________________________ poppler mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/poppler
