Why is text saved as outlines a concern for proofing and editing?

Why is text saved as outlines a concern for proofing and editing?

• A. Outlines prevent font substitution checks and edits; may inflate file size; preflight should flag unless explicitly required.
• B. Outlines ensure easy edits later.
• C. Outlines improve color fidelity.
• D. Outlines reduce file size dramatically.

Answer: (A)

Text saved as outlines becomes vector shapes rather than actual text, so proofing and editing can’t operate on the words themselves. When text is outlines, you lose the ability to spell-check, hyphenate, search, or edit content easily because there are no characters to treat as text anymore. You also can’t reliably verify fonts through substitution checks, since the document no longer carries text with font metadata—the appearance is locked to the outlines. That’s why outlines tend to blow up file size: each glyph is stored as a detailed shape rather than referenced as a font, so a long passage can become a much heavier vector graphic. Preflight tools flag outlines because they hinder proofing and editing workflows unless there’s a specific production reason to keep them in place. In short, outlines block editing and automated text checks, complicate font verification, and can unnecessarily inflate the file, which is why they’re flagged in proofing contexts.

Text saved as outlines becomes vector shapes rather than actual text, so proofing and editing can’t operate on the words themselves. When text is outlines, you lose the ability to spell-check, hyphenate, search, or edit content easily because there are no characters to treat as text anymore. You also can’t reliably verify fonts through substitution checks, since the document no longer carries text with font metadata—the appearance is locked to the outlines.

That’s why outlines tend to blow up file size: each glyph is stored as a detailed shape rather than referenced as a font, so a long passage can become a much heavier vector graphic. Preflight tools flag outlines because they hinder proofing and editing workflows unless there’s a specific production reason to keep them in place.

In short, outlines block editing and automated text checks, complicate font verification, and can unnecessarily inflate the file, which is why they’re flagged in proofing contexts.