> > Even if this is a Java bug, being able to detect which PDFs suffer from it > would be helpful. At least then you could warn users instead of them > running into silent failures.
I don't yet know how to detect this issue, but since the producer of the PDF -- PitneyShip -- could end up sending other similarly created PDFs to other Java apps, simply knowing that the problem exists is often half the battle. At time of writing this, I have not yet made an attempt to reach out to the PDF authors (I don't directly use this service). The fact that it only affects MacOS is likely why it's gone so long undetected. In the case of the company/person that reported this, they had been unknowingly/accidentally rasterizing the PDF up until discovery, so there's at least a viable workaround.
