And another.... in cwt.font.FontEnvironment.loadFontFile() the comparison (line 174) should be case insensitive on Windows otherwise getCanonicalPath() and getAbsolutePath() might differ unnecessarily. By using the new(ish) java.nio.Path interface this is handled better. And fixing this also fixed the font loader problem.
I've had a closer look. It seems that cwt.font.PlatformFontTools doesn't consider descendant fonts when looking things up. Of course that might be right, but the pdFont there is still the Type-0 font.
Thanks. I'll check the font path. Normal usage is on a Windows 7 Enterprise device. The Acrobat Pro tweak took place on a Mac, though. On all platforms imu17.pdf displays rubbish. imu17-fix.pdf had the font included by Acrobat and displays OK on my Mac. I will test on Windows next week.
I have a PDF which contains a Type0 CID font but where the secondary font (Arial) seems not to be included. Using JpodRender yields meaningless characters on the page. When I use Acrobat Pro to embed the missing font, all is OK. I have no control over the PDF files we deal with: some are important but very badly formatted. Similarly, Ghostscript (ps2pdf) can yield readable text but the resulting file has other issues for us. How do I get the program to use the system's Arial to see if that solves...
Just a followup: we're seeing more and more docs using transparency: I've attached a file that demonstrates it on many pages.
Thanks: I understand. It's really a print-only setting, and we're dealing with docs...
I think it's the overprint mode which acrobat is turning into a blend on re-rend...
Here's the original file. It's 15MBytes. The issue is page 3, which has the form...