<html> <head> <style></style></head> <body class='hmmessage'><div dir='ltr'>I think that if you have a PDF with CMYK colors for printing, and you want the preview on a screen to match what would be printed, you need a CMS to guide the CMYK to RGB conversion.<div><br></div><div>ghostscript had the same issue when they introduced a CMS, and they added a -dUseFastColor option to bypass the CMS (lcms2) in cases where speed is more important than correctness. <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=592047c6c30012f86ada508870554c9eff9a749a" target="_blank">http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=592047c6c30012f86ada508870554c9eff9a749a</a></div><div><br></div><div>Regards, William<br><br><div>> From: politza@hochschule-trier.de<br>> To: poppler@lists.freedesktop.org<br>> Date: Sat, 5 Dec 2015 22:25:19 +0100<br>> Subject: [poppler] CMS and render performance<br>> <br>> <br>> Hi,<br>> <br>> lately I did some simplistic render benchmarks using poppler-qt4. In<br>> at least one case around 30% of the time it takes to display one page<br>> was apparently spend in libcms2 .<br>> <br>> Seeing that this feature seems to vastly influence performance, I was<br>> wondering: What are the benefits of CMS for a user using an ordinary<br>> display ? And would it be prudent to make it optional at run-time,<br>> giving the user a choice ?<br>> <br>> Please excuse any ignorance I may displayed in this post.<br>> <br>> -ap<br>> _______________________________________________<br>> poppler mailing list<br>> poppler@lists.freedesktop.org<br>> http://lists.freedesktop.org/mailman/listinfo/poppler<br></div></div> </div></body> </html>