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. 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. http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=592047c6c30012f86ada508870554c9eff9a749a Regards, William
> From: [email protected] > To: [email protected] > Date: Sat, 5 Dec 2015 22:25:19 +0100 > Subject: [poppler] CMS and render performance > > > Hi, > > lately I did some simplistic render benchmarks using poppler-qt4. In > at least one case around 30% of the time it takes to display one page > was apparently spend in libcms2 . > > Seeing that this feature seems to vastly influence performance, I was > wondering: What are the benefits of CMS for a user using an ordinary > display ? And would it be prudent to make it optional at run-time, > giving the user a choice ? > > Please excuse any ignorance I may displayed in this post. > > -ap > _______________________________________________ > poppler mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/poppler
_______________________________________________ poppler mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/poppler
