> > It's mostly in PageDrawer.java search for things line width and clip.
I attempted to make some modifications to PageDrawer, but couldn't figure out any changed that improved the behavior. Also convert the PDF to uncompressed and try to change the page content > stream so that only the lines remain, i.e. try to get a "reduced" PDF that > still produces the effect. The original PDF was encrypted, so this was impossible, but Pitney Bowes was kind enough to send over an unencrypted PDF. Since I do not know the PDF format very well, I'm a bit unsure how to make sure it's uncompressed. Using Acrobat Pro, I was able to remove many of the components of the PDF while still reproducing the issue. If I remove too many of them, Acrobat turns the PDF into an image, so this "reduced" PDF still has many items which can be removed to narrow this down. https://github.com/qzind/tray/files/13229981/pitney_bowes_simplified.pdf This new PDF is interesting because a similar issue with vanishing lines occurs on the box around the C005 text, which makes me believe the issue will be even easier to narrow down. Another detail that I find interesting is how these lines render in Adobe Acrobat. For example, when I stretch the line to be larger, it looks very odd. I've taken a screenshot from Acrobat to illustrate this: https://user-images.githubusercontent.com/6345473/279754645-d406b70f-5ff1-430f-88ba-868efdf79973.png ... Furthermore, resizing of this line nearly deadlocks Acrobat on my computer. I'm not a regular user of Acrobat, so this may be irrelevant, but it seemed odd that a trivial resize operation on a document with a single line would be so taxing. Is the PDF now in a better format for debugging? If not, what can be done to help narrow down this cause?
