FS#50237 - [poppler] cannot render a particular PDF document
Attached to Project:
Arch Linux
Opened by Anonymous Submitter - Wednesday, 03 August 2016, 06:26 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 05 August 2016, 19:58 GMT
Opened by Anonymous Submitter - Wednesday, 03 August 2016, 06:26 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 05 August 2016, 19:58 GMT
|
Details
I'm running poppler-0.42.0-1 and evince-3.20.1-1.
I usually have no problem with this software combination, but now I found a PDF document that poppler/evince can't render correctly. Some text can't be read and embedded images aren't shown. The PDF document can be retrieved here: https://www.fturco.net/linux.pdf I also tried to open this PDF with other programs (Mupdf and PDF.js) and they were able to display it correctly. So such PDF is not corrupt as far as I know. I tried bypassing evince and producing a PNG image from the PDF document with pdftocairo: pdftocairo -png linux.pdf -singlefile You can download the PNG image here: https://www.fturco.net/linux.png So I tried rebuilding poppler-0.42.0 with the following options: 1) --enable-libopenjpeg=openjpeg1: pdftocairo produces warnings and a broken PNG file 2) --enable-libopenjpeg=openjpeg2: pdftocairo produces a good PNG file with no warnings at all 3) --enable-libopenjpeg=auto: it selects version 1; pdftocairo produces warnings and a broken PNG file I suggest to add --enable-libopenjpeg=openjpeg2 to the PKGBUILD as it seems better. Please also see: - https://bugs.freedesktop.org/show_bug.cgi?id=97183 - https://bugzilla.gnome.org/show_bug.cgi?id=769380 |
This task depends upon
FS#47687!But time has progressed and I see Fedora and even Debian are using openjpeg2 now in their latest branches.
I would prefer upstream recommending this over old openjpeg (1). There was a question on the poppler ml without answer lately.
Maybe I will make the switch once the poppler 0.46.0/glew rebuilds are done.