<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - Add option to manually disable bilinear filtering" href="https://bugs.freedesktop.org/show_bug.cgi?id=68360#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - Add option to manually disable bilinear filtering" href="https://bugs.freedesktop.org/show_bug.cgi?id=68360">bug 68360</a> from <a class="email" href="mailto:dr.hyder@gmail.com" title="Charles Hyder <dr.hyder@gmail.com>"> Charles Hyder</a> <pre>(In reply to <a href="show_bug.cgi?id=68360#c15">comment #15</a>) > Ok, sorry my bad, yes > ./utils/pdftoppm -r 400 -png ~/page.pdf lolo > > Does hit the bilinear filtering path. Again, I don't really understand why raster graphics needs any bilinear filtering since, as I wrote, the good old pixel mixing (I assume that's what the old code used) is the natural way to go. Rendering vector graphics, again, is a different matter, though. > So the new name of the bug + > enhacement category should fix the thing for you and get the old behaviour. > > Now, are you guys interested in coding this feature? "Guys" is just myself. > Should be a matter of > no more than 50 lines, basically a settter to SplashOutputDev, a setter to > Splash, modifying isImageInterpolationRequired and making pdftoppm set that > option if needed + the manpage change. I might. However, the issue is not very high on my personal priorities list since I'm all set using the Poppler v 0.20 for now and unless Adobe releases an update to their PDF spec such that the old Poppler code won't render it I won't feel any pressure really.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>