Comment 4 for bug 168658

After some incidents with this "feature" I changed my mind about this issue: This is a bug, not a feature request.
A missing font should be replaced by the default font but the text elements with missing fonts should be marked so the user notice that a substitution took place.
A designer choose a font family because he wants that font for his design, not a similar font or another one, and if the font isn't present in the computer that opens the file, then there is a problem and the appearance of the original design isn't preserved.
The substitution should be performed only to assure the editability of the text, not to fix the problem automatically. There are so many variations of popular families that is possible that a substitution for a font with a similar name ends up in a complete mess (there are minor width variations between similar fonts that may break the appearance of a text block, displacing words beyond the box limits, for instance).
The user has to know that the text was replaced. The XML tree keeps the name of the original font, even after a substitution, so it shouldn't be a big deal to detect a text element with a font mismatch and apply some highlighting.
The result of an overlooked font substitution can be a real catastrophe if the design goes to a print shop. And that sounds pretty bad to me, enough to turn this wishlist item into a high priority bug.