Andreas,
You said:
I won't reopen PDFBOX-483 without knowing more details on your issue. I could be related,
but probably it's just a sideeffect which only appears if clipping is actviated/deactivated.
Is it possible to provide us with a sample document?
That's only fair. You've got the document. I'm using the PDF that I
attached to PDFBOX-490. (Sorry I didn't say so earlier.)
If memory serves, when I opened PDFBOX-490, I got the current behavior
until I commented out W/W* whereupon I started getting text output, but
in the wrong typeface.
Is there any place I should look in the code to follow up on your
clipping activated/deactivated conjecture?
Hmmm, I've made similar experiences in an other case [1]. Everything worked
fine displaying the pdf
using PDFReader, but if I tried to print the pdf some of the content got lost.
Perhaps you're running in the same issue, or perhaps your hack is the problem?
The possibility that my hack is at fault weighs heavily on my mind. I'll
drop back to the current trunk version and repeat my experiment. (I'm
not seeing any NullPointerException as described in PDFBOX-552.)
During my investigations concerning [1] I've learned that displaying and
printing could be quite different things.
Both are using the (PDFBox) code for rendering but the used Graphics2d (there
are different classes used for
displaying and printing within the JDK). Furthermore the result may depend on
the used printer driver/OS/JDK.
What environment are you using?
I feel you're onto something about the distinction between printer vs
display draw code.
I'm running Windows XP, JDK 1.6.0_17, and printing to the HP LaserJet 4.
