Challenge 2: Text Looking Wrong on the Client's Machine Despite a PDF Export — Solution Walkthrough

The answer:

Per this chapter's own warning box, exporting to a format like PDF
doesn't automatically handle font dependency the way outlining does.
Since the colleague skipped Chapter 8's own outlining step, the live
text in the exported PDF still depends on the original font being
installed wherever the file is opened — and the client's machine
apparently didn't have it, so the text rendered incorrectly.

Why the PDF export alone wasn't enough:

PDF is a broadly compatible, vector-preserving format, but preserving
vector data isn't the same as removing a font dependency. Live text
stored as characters referencing a font (per Chapter 8's own material)
carries that dependency into the exported file itself unless it was
specifically outlined beforehand.

What should have happened instead:

Per this chapter's own guidance, outlining text before export — not
instead of exporting carefully — is what actually guarantees a design
looks identical everywhere. Converting the live text to paths (Create
Outlines / Object to Path) before exporting to PDF would have removed
the font dependency entirely, exactly as it did in Chapter 8's own
material.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that incorrect text rendering after a PDF export
is correctly traced back to a skipped outlining step, not to a
limitation of the PDF format itself.