<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - pdftoppm doesn't render eci_altona-test-suite-v2_technical2_x4.pdf correctly" href="https://bugs.freedesktop.org/show_bug.cgi?id=68986#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - pdftoppm doesn't render eci_altona-test-suite-v2_technical2_x4.pdf correctly" href="https://bugs.freedesktop.org/show_bug.cgi?id=68986">bug 68986</a> from <a class="email" href="mailto:Thomas.Freitag@alfa.de" title="Thomas Freitag <Thomas.Freitag@alfa.de>"> Thomas Freitag</a> <pre>A few additional remarks to test "D": if pdftoppm is just called with -png, and so splash works internally with RGB, the result for line 3 of this test (the gray shown squares) is incredible, even with the solution for <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Poppler ignores rendering intents and always uses INTENT_RELATIVE_COLORIMETRIC" href="show_bug.cgi?id=34053">bug 34053</a>: there is nearly no difference / contrast in the gray values. The reason for this is in my opinion that the background color gray is produced DeviceCMYK 0.32/0.32/0.32/0.32. If we compile poppler with #define SPLASH_CMYK 1 and then call pdftoppm with -png -overprint (only reason for the usage of the overprint option is to force splask working in CMYK mode) the rendering result is much better. (in my eyes an additional reason to remove the define and always compile the SPLASH_CMYK branch!) Therefore I will not search for a solution!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>