Forums

[rich apollo]

We get A LOT of PDFs from various Windows apps (Word, Publisher and the like) that contain numerous hard returns. Think of hitting a bunch of returns to move the type insertion point down the page. The problem that arises is that the font used for the returns is not embedded. So, of course it throws a red flag during preflight - and those red flags have to be investigated.

In testing with InDesign, I built a document with:

type
<return>
type
<return>

et cetera. I changed the fonts used for the returns to a host of different typefaces that were used only for those returns.

When I printed to file and Distilled, and when I exported directly to PDF, the resulting files excluded the returns altogether. The type showed up as separate lines of disconnected text.

So, is there a way to:

1) get these fonts that are used only for returns to embed?
2) exclude these fonts that are used only for returns?
3) alter Acrobat's Preflight to ignore instances of unembedded fonts that are used only for returns?

I'm looking for automated ways to handle this.