Forum Discussion
Poor text rendering in PDFs
Mid 2021 update: This issue is still very much with us. My system details are as follows:
- Windows 10 Education, 20H2
- 1440p display on 125% scaling
- Edge Version 92.0.902.55 (Official build) beta (64-bit)
I am still forced (objectively, it's not a breaking issue, but it is so given an obsessive personality) to use Firefox when it comes to working with PDF documents on Overleaf.
My question to anyone reading this: Has this really NEVER occurred to you? If so, what are your system details?
The non-100% display scaling is the only thing I can think of that might have something to do with this, and the high resolution screens are so common nowadays that I think most of you should already be in the same boat as mine. And in my boat, it seems that one has to be very lucky to not have the issue, or be very carefree about it to not have a notice.
I have the same problem - texts become broken and it gets fixed on selection, that is, the text gets rendered again (and slightly shifts). It seems to be most noticeable on italics.
The problem occurs on e-book "Practical SQL (No Starch Press)" in PDF format,
but the problem doesn't seem to be specific to this single file.
The rendering of texts become broken when zoomed in, but I can't say for sure it doesn't happen at 100% because the texts are too small to discern broken rendering.
I've attached a screenshot of the broken text.
It's a minor problem, but I can't help myself "fixing" the broken texts by selecting them. It's like.. popping bubbles.
Anyway, the system environment is provided below.
Environment:
- Edge build 94.0.992.31 (64bit)
- Windows 10 Enterprise 20H2 build 19042.541
- Two monitors (2560x1440 ViewSonic, 1920x1080 LG) connected via HDMI
- HP Desktop with Intel(R) UHD Graphics 630 as integrated, NVIDIA GeForce RTX 2080 as discrete
- No known issues with graphics card or its connections
No issues reading the same PDF file with Chrome, Firefox, ADOBE PDF Reader, and Hancom PDF Reader.
btw, is there a tracking number for this bug?
