I've got a few PDF's that display bad /BBox errors when certain pages are displayed:
It has happened with a few different fonts on different pages, but always with fonts that have the {6 character string}+{Font Name} style name.
When I look at the page font resource by browsing the PDF document structure with the Preflight tool in Acrobat X, I see that the font that is in the alert message doesn't have a font descriptor - which I think is causing the errors to be fired.
(See picture: No font descriptor in the PalatinoLinotype-Bold font resource)
The workflow through which these pages are produced is somewhat involved, including some text being rendered with an in-house C++ plugin, as well as page content being rendered with Distiller in some cases and iText (via a java application) in others. We are also currently in a mixed enviroment where legacy users are using Acrobat 8.2.5 and some users are using Acrobat X (I believe most users are on 10.1.4).
I have inhereted much of the code from the in-house plugin, so in some ways I am just figuring out how to debug our code appropriately, while at the same time trying to learn as much as I can about font handling in PDFs. I have more research to do for sure, but I just wanted to ask the community:
Generally speaking, are there well understood patterns that lead to font resources ending up without a Font Descriptors?
Apologies if my question is too vague, and thanks for any thoughts anybody might have.