Created attachment 100366 [details] The problematic PDF file rendered by 2 version of pdftoppm A certain image in PDF is rendered as garbage by pdftoppm. Other images are rendered fine. Tested with pdftoppm version 0.26.0 which was compiled on Win XP with cairo_1.10.2-2 freetype_2.4.10-1 openjpeg-1.5.1 zlib_1.2.5-2 I also have pdftoppm as part of cygwin, which is pdftoppm version 0.24.5 and this version renders the example PDF just fine. The resulting images from the problematic version 0.26.0 and working version 0.25.5 are attached, along with the PDF file itself.
The version of 0.26.0 is actually the one I compiled with git master (obtained today). I have reasons to believe that something may be wrong with my local compilation process, though. So please confirm the bug first. In case it's just me, I'm following the instructions: http://laconsigna.wordpress.com/2011/07/14/compiling-poppler-on-windows/ to compile under Win XP. It this is not how the compilation should be done please tell me how to do it right.
Works fine here. I have no clue about using windows so i can't help you there.
I've narrowed the problem down to JPEG2000 images with indexed color (palette). It is not relevant to poppler itself and is probably related to my compiler (MS Visual Studio 10). Since Windows platform is not officially supported by the poppler project I'm closing this bug. I guess I'll have to use poppler windows binaries compiled by others as they seem to work just fine.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.