Bug 64855 - Rendering unprecise -> holes in large parentheses
Summary: Rendering unprecise -> holes in large parentheses
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: poppler-bugs
QA Contact:
Depends on:
Reported: 2013-05-22 08:59 UTC by Patrick Häcker
Modified: 2018-08-21 10:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Problematic PDF file (37.97 KB, application/pdf)
2013-05-22 10:06 UTC, Patrick Häcker
Cropped problematic PDF (31.48 KB, application/pdf)
2013-05-22 12:38 UTC, Patrick Häcker
PNG converted from PDF (4.09 KB, image/png)
2013-05-22 12:39 UTC, Patrick Häcker
Zoomed PNG file (converted from PDF) (8.45 KB, image/png)
2013-05-22 12:41 UTC, Patrick Häcker
Generated with 'pdftoppm -r 94' (2.06 KB, image/png)
2013-05-22 13:34 UTC, Patrick Häcker
Generated with 'pdftoppm -r 154' (3.60 KB, image/png)
2013-05-22 13:36 UTC, Patrick Häcker
Generated with 'pdftoppm -r 154' with poppler 0.18.4 (3.53 KB, image/png)
2013-05-22 13:38 UTC, Patrick Häcker
Another example of imperfections (45.44 KB, text/plain)
2013-05-31 07:18 UTC, Marco

Description Patrick Häcker 2013-05-22 08:59:56 UTC
The rendering of a PDF file generated by LaTeX is unprecise, which leads to tiny holes in large parentheses as described here http://tex.stackexchange.com/q/115260. As this is reproducible in all tested poppler viewers including xpdf, but cannot be reproduces with mupdf, this seems to be a poppler issue. Unfortunately, I do not know poppler good enough to describe the problematic component, but it occurs in Okular, for example.
Comment 1 Albert Astals Cid 2013-05-22 09:33:07 UTC
Where's the pdf file?
Comment 2 Patrick Häcker 2013-05-22 10:06:06 UTC
Created attachment 79645 [details]
Problematic PDF file
Comment 3 Patrick Häcker 2013-05-22 10:07:32 UTC
Sorry, for forgetting that. I just appended it (hole.pdf).

Just for clarity: The effect can only be seen with some zoom values (here for 
example in Okular with 200% and 300% but not with 255%)

In case it is important:
Poppler version: 0.18.4
Comment 4 Albert Astals Cid 2013-05-22 10:51:47 UTC
Works for me, or at least can you attach an image showing the problem?

Also you're using a version that is two major releases behind, so yes, obviously it matters
Comment 5 Patrick Häcker 2013-05-22 12:38:11 UTC
Created attachment 79652 [details]
Cropped problematic PDF

generated with pdfcrop (from Debian package: texlive-extra-utils)
Comment 6 Patrick Häcker 2013-05-22 12:39:59 UTC
Created attachment 79653 [details]
PNG converted from PDF
Comment 7 Patrick Häcker 2013-05-22 12:41:20 UTC
Created attachment 79654 [details]
Zoomed PNG file (converted from PDF)

The red highlighting of the problematic areas has been done manually
Comment 8 Patrick Häcker 2013-05-22 12:53:08 UTC
I created a cropped variant of the PDF file (without the page number), to focus on the problem at hand ("Cropped problematic PDF").

I checked out the git version of poppler to confirm, that the problem still exists. As I don't have a viewer capable of handling the most recent poppler version, I used the "pdftocairo" tool to generate a PNG file from the PDF file with the following command:
./pdftocairo -r 170 -png hole-crop.pdf ~hole-crop

This lead to the attachment "PNG converted from PDF". To highlight the problem, I marked the problematic areas with red color and zoomed-in, which can be seen in "Zoomed PNG file (converted from PDF)".

The problem seems to be more obvious in Okular (but this might be due to the older poppler version): http://tex.stackexchange.com/q/115260

I hope you can reproduce the problem with the above instructions. Please note, that the resolution option in the "pdftocairo" command is very critical. I did not see the problem for "-r 171", for example.
Comment 9 Albert Astals Cid 2013-05-22 13:07:17 UTC
Okular and pdftocairo use different renderers, can you please see if you can reproduce with pdftoppm too (which uses the same renderer as Okular)?
Comment 10 Patrick Häcker 2013-05-22 13:34:54 UTC
Created attachment 79655 [details]
Generated with 'pdftoppm -r 94'
Comment 11 Patrick Häcker 2013-05-22 13:36:33 UTC
Created attachment 79656 [details]
Generated with 'pdftoppm -r 154'
Comment 12 Patrick Häcker 2013-05-22 13:38:16 UTC
Created attachment 79657 [details]
Generated with 'pdftoppm -r 154' with poppler 0.18.4
Comment 13 Patrick Häcker 2013-05-22 13:44:22 UTC
Yes, the problem can also be seen with pdftoppm ("Generated with 'pdftoppm -r 94'" and "Generated with 'pdftoppm -r 154'"). You possibly have to zoom-in to detect it.

With recent poppler versions the problem seems to be less critical and occurs only for a small number of low-resolutions. With poppler 1.18.4, the problem is more severe ("Generated with 'pdftoppm -r 154' with poppler 0.18.4") and also occurs for higher resolutions.
Comment 14 Marco 2013-05-31 07:18:02 UTC
Created attachment 80083 [details]
Another example of imperfections
Comment 15 Marco 2013-05-31 07:19:44 UTC
Hi guys, I can confirm this problem. I added file "Curly brackets and square root" where you can find other imperfections. Maybe you need to try different levels of zoom to see them. Pdf has been generated with pdflatex and does not show these defects with Adobe Reader.
Comment 16 Patrick Häcker 2013-05-31 07:41:41 UTC
Yes, I probably forgot to mention, the problem can always happen when two line/curve segments are placed next to each other.

@Marco, thanks for the additional information. It would be good if you could add information about the viewer you used (okular?), which poppler version is installed and at which zoom levels the problem can be seen (maybe even with screen shots).
One hint: You should set the MIME-Type of the uploaded files correctly, e.g. application/pdf instead of text/plain for a PDF file.
Comment 17 GitLab Migration User 2018-08-21 10:35:17 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/273.

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.